From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Location of absolute IA32 shared objects.
Date: Fri, 14 Sep 2001 14:41:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805182@msgid-missing> (raw)
Doug Beattie (dbb@caldera.com) said:
> `The /lib directory on x86 and IA64 will always contain the 32bit
> libraries. IA64 systems should put their libraries in /lib64.' "This
> way we don't need any special install hooks in the system, installer,
> and package. It's all hardcoded."
That doesn't make sense to me. For the dlopen()ing of things we're talking
about, the reasons they are hardcoded paths is because *they are not in
the standard library search path*.
Bill
reply other threads:[~2001-09-14 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105590698805182@msgid-missing \
--to=notting@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.