On Fri, 31 Oct 2014, Steve Ellcey  wrote:

> So the question is: should /lib and /usr/lib always be for the default GCC
> ABI (whatever that may be) or should /lib and /usr/lib always be for the
> MIPS (old) 32 ABI (with /lib32 and /usr/lib32 always being for the MIPS N32
> ABI and /lib64 and /usr/lib64 always being for the 64 MIPS ABI.  I chose the
> latter as it seemed clearer and more consistent and that is why I also
> needed to change mips.h to add the overrides of STANDARD_STARTFILE_PREFIX_1
> and STANDARD_STARTFILE_PREFIX_2.  These overrides are not needed if building
> a multilib GCC because then MULTILIB_OSDIRNAMES in t-linux64 takes care
> of everything, but they are needed if building a non-multilib GCC with a
> default ABI other than the old 32 bit ABI.

/lib and /usr/lib should always be for o32.

> +             if test x$with_endian != x; then
> +                     default_mips_endian=$with_endian
> +             fi

install.texi currently says --with-endian is only for SH; you'll need to 
update the documentation to say what versions of this option are supported 
for MIPS.  Also, t-linux64 uses

MIPS_EL = $(if $(filter %el, $(firstword $(subst -, ,$(target)))),el)

to determine endianness for Debian multiarch purposes, and I think this 
will need to change when you allow --with-endian to control the 
endianness.

-- 
Joseph S. Myers
jos...@codesourcery.com

Reply via email to