From: Jes Sorensen <jes@sunsite.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Location of absolute IA32 shared objects.
Date: Tue, 18 Sep 2001 08:05:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805198@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805122@msgid-missing>
>>>>> "Doug" = Doug Beattie <dbb@caldera.com> writes:
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."
It's extremely nice of the FHS people to make such decisions without
consulting with the people who actually deals with the architecture in
question. Fortunately their silly decision wont have any effect here,
native libraries go in /lib and /usr/lib. They will have to change the
spec.
Keep in mind that ia32 binaries are a compatibility issue not a 'this
is what we recommend you use forever on this system' type of thing.
Jes
prev parent reply other threads:[~2001-09-18 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 17:26 [Linux-ia64] Location of absolute IA32 shared objects Don Dugger
2001-09-05 20:47 ` Christoph Hellwig
2001-09-05 20:53 ` Don Dugger
2001-09-11 4:11 ` David Mosberger
2001-09-11 4:30 ` Ulrich Drepper
2001-09-11 10:26 ` Christoph Hellwig
2001-09-11 11:25 ` Mark Goodwin
2001-09-12 11:58 ` Christoph Hellwig
2001-09-13 19:52 ` David Mosberger
2001-09-14 14:30 ` Doug Beattie
2001-09-14 15:51 ` David Mosberger
2001-09-14 21:26 ` Dugger's
2001-09-17 20:33 ` David Mosberger
2001-09-18 8:05 ` Jes Sorensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805198@msgid-missing \
--to=jes@sunsite.dk \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox