From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Wolverine RPMs
Date: Wed, 05 Sep 2001 16:47:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805121@msgid-missing> (raw)
Bill raises an interesting problem. I'd like to suggest a solution and see
what everyone thinks. Since all of the shared objects are loaded by code
in `ld-linux.so' I can modify the IA32 version of that library to first try
an absolute path and, if that fails, because it's missing or has the wrong
architecture, to then tack on a unique prefix, either something like
`/usr/ia32' or the contents of an environment variable like `LD_IA32_PATH'.
This is a little ugly since all of the distro's would have to install s
special version of `ld-linux.so' but at least this is just one library
so that cuts the pain down a little bit.
Does anyone have a better idea?
On Wed, Sep 05, 2001 at 11:59:31AM -0400, Bill Nottingham wrote:
>
> The biggest problem I've seen is with programs that have hardcoded paths
> for shared objects they dlopen(). Obviously this fails pretty badly when
> the ia32 binary trys to dlopen() an ia64 library.
>
> Notably, this affects GTK+ when trying to use themes, and anything that
> uses PAM.
>
> Bill
>
>
>
> _______________________________________________
> ia64-list mailing list
> ia64-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/ia64-list
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838
next reply other threads:[~2001-09-05 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 16:47 Don Dugger [this message]
2001-09-05 17:57 ` [Linux-ia64] Re: Wolverine RPMs Doug Beattie
2001-09-05 19:20 ` Saxena, Sunil
2001-09-10 9:21 ` Jes Sorensen
2001-09-10 17:15 ` Christoph Hellwig
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-105590698805121@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