This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG 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]

Re: mips 32 24kec eabi. . .


On 02 Jul 2015 18:14, ANDY KENNEDY wrote:
> I derived a patch that I stole from the ARM folks for their eabi
> settings.  I have the ability to make an elf toolchain that is eabi.
> When attempting to build a Linux glibc toolchain, I get errors on the
> tuple for building the base glibc as it doesn't understand
> mipsel-linux-gnueabi.  Digging into the goings on I see the error
> -mabicalls conflicts with -mabi=eabi.  I have searched every way I can
> think of to locate the -mabicalls (which is the same as -mnoabicalls if
> you didn't already know that) but it is not physically located in the
> source of ct-ng.  Where is this coming from?
> 
> The comments around the selection for eabi state that this is not
> applicable for mips, however, for my embedded processor, it is.  In
> fact, this is a valid configuration according to the information from
> gcc and (I think) also glibc. . .
> 
> Anyone have any ideas on where we are getting the -mabicalls?

glibc itself enforces one of three -mabi settings:
sysdeps/mips/mips32/Makefile:CC += -mabi=32
sysdeps/mips/mips64/n32/Makefile:CC += -mabi=n32
sysdeps/mips/mips64/n64/Makefile:CC += -mabi=64

that's going to conflict with -mabi=eabi.
-mike

Attachment: signature.asc
Description: Digital signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]