From: Christoph Hellwig <hch@ns.caldera.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Location of absolute IA32 shared objects.
Date: Wed, 05 Sep 2001 20:47:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805128@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805122@msgid-missing>
On Wed, Sep 05, 2001 at 02:53:11PM -0600, Don Dugger wrote:
> 2) How do we deal with absolute path names in IA32 binaries? This is
> the question I'm concerned with right now. The sad reality of life is
> that there are rogue (I use the term `rogue' with tongue firmly planted
> in check) IA32 binaries that have hard coded absolute paths to certain
> libraries. I think we all agree that `standard' libraries must be IA64
> objects and, therefore, we need to find a way to deal with these
> rogue IA32 programs if we want them to run.
>
> I have a proposed solution to 2 but it's not perfect. I was kind of hoping
> that someone had a better idea but it doesn't look like it. Unless someone
> comes up with a brainstorm I'll implement my idea and at least we should
> be able to run the rogue IA32 programs we know about.
Please take a look at include/asm-*/namei.h - we can define an emulation
prefix for Linux/i386 (e.g. /emul/linux32) and all lookups will be tried
there before falling back to the native FS, This appropeach is already
used by the MIPS and SPARC ports and by linux-abi for i386.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-09-05 20:47 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 [this message]
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
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-105590698805128@msgid-missing \
--to=hch@ns.caldera.de \
--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