Re: Multilib directory of n32 libs
Any idea about is there another distribution has n32 or n64 port, and
at the same time that multilib is supported?
If there is one, maybe we should fellow it.
If no, maybe we can consider that
libo32 -> o32
lib32 -> n32
lib64 -> n64
On Sat, Jun 8, 2013 at 10:03 AM, YunQiang Su <wzssyqa@gmail.com> wrote:
> On Sat, Jun 8, 2013 at 12:33 AM, David Daney <ddaney@caviumnetworks.com> wrote:
>> On 06/07/2013 05:49 AM, Eleanor Chen wrote:
>>>
>>> Hi everyone,
>>>
>>> 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
>>> discuss.
>>>
>>> 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:
> We have both the 2 situations.
>>
>> o32 -> /lib and /usr/lib
> This path is should be used by the current arch on Debian.
>>
>> n32 -> /lib32 and /usr/lib32
>>
>> n64 -> /lib64 and /usr/lib64.
> Is there any other distributions that support several mips* architecture?
>>
>> 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 MIPS32
>> Debian.
>>
>> 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
>>
>>
>> David Daney
>>
>>
>>>
>>> Best Regards,
>>> Eleanor
>>>
>>>
>>>
>>
>>
>
>
>
> --
> YunQiang Su
--
YunQiang Su
Reply to: