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] |
On Wednesday 18 January 2012 02:09:09 Zhenqiang Chen wrote: > > -EL is only valid for mips gcc as far as ct-ng is concerned. It should > > not be used for arm configurations since arm is little endian by > > default pluis this is an invalid option you need > > -mlittle-endian for arm if you really want to specify it explicitly. > > -EL/-EB is added in crosstool-ng automatically. Here is the code > segment in scripts/functions > > CT_DoBuildTargetTuple() { > # Set the endianness suffix, and the default endianness gcc option > case "${CT_ARCH_ENDIAN}" in > big) > target_endian_eb=eb > target_endian_el= > CT_ARCH_ENDIAN_CFLAG="-mbig-endian" > CT_ARCH_ENDIAN_LDFLAG="-EB" > ;; > little) > target_endian_eb= > target_endian_el=el > CT_ARCH_ENDIAN_CFLAG="-mlittle-endian" > CT_ARCH_ENDIAN_LDFLAG="-EL" > ;; > esac LDFLAGS should take the form as needed by the compiler driver. i.e. -Wl,-EL. i'm guessing some other code takes care of transforming this before exporting LDFLAGS to the build ? -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |