From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Location of absolute IA32 shared objects.
Date: Wed, 05 Sep 2001 20:53:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805127@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805122@msgid-missing>
I think there are two issues here, both important, but I was only trying
to address the second question:
1) Exactly where do we put IA32 objects. Personally I don't care,
to me this is just an arbitrary character string that needs to be added
to path names and I use which ever one everybody agrees to. Unfortunately
the Itanium specific ABI suggests where to put them but it doesn't
explicitly specify where. The ABI only talks about IA64 objects, it
doesn't explicitly deal with IA32 objects. A quick read of section
5.3.1 would say to me that `/usr/lib/ia32', `/usr/lib/ia32l32',
`/usr/lib/ia32l' or `/usr/lib/l32' are all possible interpretations of
where IA32 objects are placed. Again, I don't care, pick one. Doug
is right, this is something that should be coordinated with the LSB.
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.
On Sep 05, 2001 at 12:20:01PM -0700, Sunil Saxena wrote:
> Have you folks looked at the "UNIX System V Application Binary Interface" at
> http://developer.intel.com/design/IA-64/ ? Section 5.3.1 suggests locations
> for the libraries.
>
> Thanks
> Sunil
>
> -----Original Message-----
> From: Doug Beattie [mailto:dbb@caldera.com]
> Sent: Wednesday, September 05, 2001 10:57 AM
> To: Don Dugger
> Cc: Bill Nottingham; ia64-list@redhat.com; linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] Re: Wolverine RPMs
>
>
> Don and others:
>
> Let's not forget what might need to be considered to allow LSB 32 bit
> compliant apps on IA64. Even though no one may ever certify for this,
> it would be nice to find out and follow a convention that would
> benefit all.
>
> Doug
>
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
next prev parent reply other threads:[~2001-09-05 20:53 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 [this message]
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-105590698805127@msgid-missing \
--to=n0ano@valinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox