From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PROPOSED: 32/64 bit coexistance
Date: Wed, 19 Sep 2001 21:43:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805227@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805199@msgid-missing>
>>>>> On Wed, 19 Sep 2001 02:02:35 -0400, Jakub Jelinek <jakub@redhat.com> said:
Jakub> On Tue, Sep 18, 2001 at 01:47:12PM -0700, David Mosberger
Jakub> wrote:
>> That would be good. It might also be good to explicitly state
>> that these trees are expected to follow the filesystem layout
>> conventions of the emulated environment (to the degree that this
>> makes sense). For example, you could assume that there would be:
>>
>> /emul/ia32-linux/etc/ld.so.conf
Jakub> Why ld.so.conf? /etc/ld.so.conf should be enough when
Jakub> ldconfig handles multiple ABI libraries.
I think there is a choice. You could do it either way (theoretically
at least). From a user perspective, it's probably better to have just
/etc/ld.so.conf.
--david
prev parent reply other threads:[~2001-09-19 21:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 8:34 [Linux-ia64] Re: PROPOSED: 32/64 bit coexistance Andreas Jaeger
2001-09-18 9:00 ` Theodore Tso
2001-09-18 9:21 ` Luigi Genoni
2001-09-18 9:39 ` Jakub Jelinek
2001-09-18 10:06 ` Jakub Jelinek
2001-09-18 16:33 ` David Mosberger
2001-09-18 16:57 ` Christoph Hellwig
2001-09-18 17:22 ` David Mosberger
2001-09-18 17:50 ` Andreas Jaeger
2001-09-18 19:33 ` David Mosberger
2001-09-18 20:07 ` Andreas Jaeger
2001-09-18 20:25 ` Christoph Hellwig
2001-09-18 20:47 ` David Mosberger
2001-09-18 20:53 ` David Mosberger
2001-09-18 21:05 ` Joseph V Moss
2001-09-19 6:02 ` Jakub Jelinek
2001-09-19 21:43 ` David Mosberger [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-105590698805227@msgid-missing \
--to=davidm@hpl.hp.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.