Re: Multilib directory of n32 libs

On 06/08/2013 11:24 PM, YunQiang Su wrote:
> On Sun, Jun 9, 2013 at 1:57 PM, Matt Turner <[email protected]> wrote:
>> On Sat, Jun 8, 2013 at 7:23 PM, YunQiang Su <[email protected]> wrote:
>>> On Sun, Jun 9, 2013 at 12:23 AM, Matt Turner <[email protected]> wrote:
>>>> On Sat, Jun 8, 2013 at 8:54 AM, YunQiang Su <[email protected]> wrote:
>>>>> Any idea about is there another distribution has n32 or n64 port, and
>>>>> at the same time that multilib is supported?
>>>>
>>>> Yes, Gentoo. We do the standard o32 -> lib, n32 -> lib32, n64 -> lib64.
>>> Is there a port to n32 or n64 of gentoo?
>>> On n32 or n64 port, is it fit to put o32 libraries into lib directly?
>>
>> Yes, I have n32-multilib (n32 base system, and n64 and o32 glibc and
>> gcc libraries) and n64. o32 goes in lib regardless of the ABI of the
>> base system.
> It is not forbid to put o32 libraries to /lib in mips64 port in policy
> (Fix me if I am wrong).

OK: I think you are wrong here.

o32 libraries must go in /lib and /usr/lib as Matt and I have already 
told you.

If the mips64 port policy disagrees with this, then the policy is 
incorrect and must be changed.


> While as ldso will always looks for /lib and /usr/lib/, thus if we put
> it in /libo32,

No, I think you misunderstand how ld.so works.

ld.so looks in the proper directories already, and functions perfectly 
with the library directories named as Matt and I have told you.


> it will still work and packages built on other distributions(like
> packages converted by alian).
>
> And the Debian package would not work on other distributions where
> /libo32 is not supported,
> Since we have multiarch support, this is not a big problem ;)

If you are using multi-arch, then all of this is moot.  You need to use 
the proper multi-arch directories instead.

David Daney