This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> -----Original Message----- > From: ANDY KENNEDY > Sent: Thursday, March 03, 2011 5:18 PM > To: 'crossgcc@sourceware.org' > Subject: RE: CrossTool-NG (working towards getting a few Mips toolchains) > > My apologies, I don't get messages I send to the list, so if this > shows up as a new thread, that is why. Cool! It shows up right after all. > 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. > 123456789012345678901234567890123456789012345678901234567890123456789012 Okay, so now I see that mips-*-linux-gnu is not the same as the big-endian counterpart mips32r2. So, in crosstool-NG.sh, I attempt to brute force the issue by setting mips32r2-unknown-linux-gnu as the tuple. For some reason, however, when I do this, I get something (I think it is gcc giving me the TARGET=mips642r2-unknown-linux-gnu. What's up with that? Andy -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |