Re: Multilib directory of n32 libs
On 06/07/2013 05:49 AM, Eleanor Chen wrote:
I am the student of this year's GSoC project "MIPS N32/N64 ABI Port".
This is my first E-mail to this mailing list. I have a question to
Here it is:
In x86 architecture's multilib configuration, we have /libx32 and
/lib32 directories respectively, however, in mips, we have /lib32 for
n32 on current mpis/mipsel ports, what about the directory for o32 on
64 bit architectures, say mips64/mips64el? Should we have a /libo32
for it or should we change the current directory of n32 to /libn32 and
make /lib32 the directory for o32?
If we are using the standard library locations (which we should, if not
doing debian multi-arch or what whatever it is called) then we must
follow the standard:
o32 -> /lib and /usr/lib
n32 -> /lib32 and /usr/lib32
n64 -> /lib64 and /usr/lib64.
Note that o32 running on a 64-bit kernel is identical to o32 running on
a 32-bit kernel, so the code and libraries are exactly the existing
If we are going to implement multi-arch (probably a good idea) Then
things will be different. Perhaps:
o32 -> /lib/mips-linux-gnu
n32 -> /lib/mips64-linux-gnuabi32
n64 -> /lib/mips64-linux-gnuabi64