RE: CrossTool-NG (working towards getting a few Mips toolchains)

[ANDY KENNEDY <ANDY dot KENNEDY at adtran dot com>]

My apologies, I don't get messages I send to the list, so if this
shows up as a new thread, that is why.


> 
-----Original Message-----
> From: ANDY KENNEDY
> Sent: Wednesday, March 02, 2011 12:57 AM
> To: 'Yann E. MORIN'
> Cc: crossgcc@sourceware.org
> Subject: RE: CrossTool-NG (working towards getting a few Mips
toolchains)
> 
> 
> > > [ALL  ]
> > >
/root/src/buildroot-retool/crosstool-ng/crosstool-ng/.build/mips-nfs_dev
> > >
el-linux-gnu/build/gcc-core-shared/lib/gcc/mips-nfs_devel-linux-gnu/4.5.
> > > 2/../../../../mips-nfs_devel-linux-gnu/bin/ld:
> > >
/root/src/buildroot-retool/crosstool-ng/crosstool-ng/.build/mips-nfs_dev
> > > el-linux-gnu/build/build-libc/csu/init.o: compiled for a big
endian
> > > system and target is little endian
> 
> >
> > I'll need your .config so I can try to reproduce the error...
> >
> > Regards,
> > Yann E. MORIN.
> 
> Yann/All:

<snip>

> I have searched and searched and have come up with the CFLAGS=-EB
doesn't
> get passed into the build-libc-startfiles make system, therefore, it
gets
> built as little endian:

So, the trick is that there is a JOBSFLAGS that is apparently unused as
all through the build process JOBSFLAGS = "".  Next, is the issue of the
config option for CT_ARCH_BE does not get passed into the eglibc
configure.

I'm wading my way through this:  There seems to be a file that is
generated
which tells the build process how to configure the CFLAGS????

All I have found for the past three days is that there is neither a -EB
nor
a -mbig-endian passed to <tuple>-gcc for compilation and my Big-Endian
crt1.o never gets built as big-endian.  Is it in the configure that the
CFLAGS needs to include -mbig-endian/-EB???

Grr, I go looking further.

Andy

 

--
For unsubscribe information see http://sourceware.org/lists.html#faq