This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Multilib build question involving MULTILIB_OSDIRNAMES


I have a multilib question that I hope someone can help me with.

If I have this multilib setup while building a cross compiler:

MULTILIB_DEFAULTS { "mips32r2" }
MULTILIB_OPTIONS = mips32r2/mips64r2
MULTILIB_OSDIRNAMES = ../lib ../lib64

Everything works the way I want it to.  I have mips32r2 system libraries
in /lib under my sysroot and mips64r2 system libraries in /lib64 and
everything seems fine.

Now I want to make mips64r2 the default compilation mode for GCC but
I want to keep my sysroot setup (/lib for mips32r2 and /lib64 for mips64r2)
the same.  So I change MULTILIB_DEFAULTS to specify "mips64r2" and rebuild.

When I do this, a default build (targeting mips64r2) searches for system
libraries in /lib instead of /lib64.  Is there a way to fix this without
having to put mips64r2 system libraries in /lib?  Is this the expected
behaviour or is this a bug in handling MULTILIB_OSDIRNAMES?

Steve Ellcey
sellcey@mips.com


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