On Wed, Feb 17, 2010 at 12:39 PM, Dr. David Kirkby
<david.kirkby@xxxxxxxxxx> wrote:
> Ben Taylor wrote:
>>
>> On Thu, Feb 11, 2010 at 11:00 AM, Konstantin Andreev <andreev@xxxxxxxxx>
>> wrote:
>
>>> In Solaris, libraries live in
>>>
>>> 32-bit : /usr/lib
>>> 64-bit : /usr/lib/64
>>
>> where 64 -> amd64 or sparcv9
>
> There's also /lib/amd64 and /lib/sparcv9. /usr/lib and /lib are *not*
> linked.
On S10, that is the case. Earlier versions of Solaris had /lib linked
to /usr/lib.
> I've noticed that some software installs files in places /usr/local/amd64 or
> /usr/local/sparcv9, but does not create the link to the "64" directory.
Most FOSS software I have dealt with has had a hard time dealing with
dual support (32/64bit). In fact, not much of the code I have built for
the KDE4 project on Solaris 10 to support KDE4 uses a 2 stage build,
which does the 32-bit then 64-bit builds in separate directories, then
layers the install to one package.
>
> It is a bit of a mess.
Yes. I think most folks just build 32-bit stuff and are done with it.
Plus, with the mess that trying to guess what lib%{64} and bin%{64}
looks like on each system, I would guess that most folks just
throw up their hands... It's probably the tangle-ist of issues
> I've got an HP-UX box here, which is not powered on at the minute, but I
> suspect HP do the 32/64 bit thing a different way. I think the 64-bit
> libraries in in something like /usr/lib/PA-2.2
As pointed out, practically all os implementations have their own way of
dealing with the 32/64 bit issue for lib and bin directories.
On a project I contribute to which uses a substantial amount of FOSS
software, we build 32/64-bit code, but we hadn't put in the "64" link to the
lib/{amd64,sparcv9} and bin/{amd64,sparcv9} directories.
I suspect that eventually, this will get better over time, as the support tools
can correctly arbitrate the lookups based on system type, as more and
more people build dual configs.
Ben
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
