Re: [Linux-ia64] Location of absolute IA32 shared objects.

["Dugger's" <ddugger@qwest.net>]

I don't normally send out agreement messages but this time I have to.  As
David said we've debated this many times in the past and the answer is
always the same.  This is an IA64 system and therefore `/lib', `/usr/lib',
`/bin',
`/sbin' and so on all contain IA64 files.  The IA32 files go elsewhere and
we
work around the issues that this creates.  Specifically where the IA32
objects
go doesn't concern me too much but I adamantly agree that they go elsewhere.
--
Don Dugger
ddugger@qwest.net
----- Original Message -----
From: "David Mosberger" <davidm@hpl.hp.com>
To: <dbb@caldera.com>
Cc: "Ulrich Drepper" <drepper@cygnus.com>; <linux-ia64@linuxia64.org>
Sent: Friday, September 14, 2001 9:51 AM
Subject: Re: [Linux-ia64] Location of absolute IA32 shared objects.


> >>>>> On Fri, 14 Sep 2001 08:30:22 -0600, Doug Beattie <dbb@caldera.com>
said:
>
>   Doug> I just noticed a comment was posted on 2001-08-15 to the LSB
>   Doug> tracking task on this subject, that a post to fhs-discuss gave
>   Doug> the solution to the question of where ia32 vs ia64 libs should
>   Doug> be placed.
>
>   Doug> `The /lib directory on x86 and IA64 will always contain the
>   Doug> 32bit libraries. IA64 systems should put their libraries in
>   Doug> /lib64.' "This way we don't need any special install hooks in
>   Doug> the system, installer, and package. It's all hardcoded."
>
>   Doug> The description above are a paraphrase and direct quote from
>   Doug> the post to LSB task number 32642 that was used to track what
>   Doug> should be done for LSB compatibility.
>
> And we already have discussed this option on the ia64 lists a long
> time ago and we rejected it due to source compatibility issues.  /lib
> and /usr/lib must contain the native libraries, period.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>