From: Mark Goodwin <markgw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Location of absolute IA32 shared objects.
Date: Tue, 11 Sep 2001 11:25:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805172@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805122@msgid-missing>
On Tue, 11 Sep 2001, Christoph Hellwig wrote:
> On Mon, Sep 10, 2001 at 09:30:02PM -0700, Ulrich Drepper wrote:
> > David Mosberger <davidm@hpl.hp.com> writes:
> >
> > > As far as I can see, neither LSB nor FHS address the issue of where
> > > to place emulation files, so I'll propose a prefix of
> > > "/emul/ia32-linux/" as a starter. Any objections?
> >
> > Not that I care, but this is clearly a place for a new /proc entry
> > which can be changed by the sysadmin.
>
> If that is the general consensus I will globally move the emul prefix
> stuff to /proc based values instead of compile-time defines.
>
> Any objections?
RPM installs for ia32 apps/libs will need to use --prefix `cat /proc/ia32prefix`
or whatever. If sysadmin subsequently changes the prefix, it wont work. Would a
better solution be an ia32 specifc version of /etc/ld.so.conf? Or perhaps the
/proc file should allow multiple search paths?
-- Mark
next prev parent reply other threads:[~2001-09-11 11:25 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 [this message]
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
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-105590698805172@msgid-missing \
--to=markgw@sgi.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.