Re: libstdc++ configure fail due to -EL option

[Mike Frysinger <vapier at gentoo dot org>]

On Monday 23 January 2012 16:08:39 Bryan Hundven wrote:
> On Wed, Jan 18, 2012 at 2:28 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > 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.
> 
> Well, we'd get the same error if we pass -Wl,-EL to ld, where that
> would fix it for passing to gcc.

yes, but generally speaking, you should not be invoking the linker.  
everything should be going through the compiler driver.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.