From: Andreas Jaeger <aj@suse.de>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: LD_ASSUME_KERNEL problem
Date: Tue, 17 Jun 2003 13:38:00 -0000 [thread overview]
Message-ID: <hoof0wrfh9.fsf@byrd.suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
The usual "hack" to switch between i686 and non-i686 libpthreads on a
x86 system is to use LD_ASSUME_KERNEL and setting it to some old
version, e.g. 2.2.5.
But if you put such libraries on a 64-bit system with i686 support
that has also a 64-bit glibc e.g AMD64 or ia64, the environment
variable will have effect on both 32-bit and 64-bit libraries and you
cannot execute anymore 64-bit code :-(
So, what can we do? We need a better way IMO to switch libraries to
not affect all installed glibcs. Any good ideas?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2003-06-17 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 13:38 Andreas Jaeger [this message]
2003-06-25 6:11 ` Roland McGrath
2003-06-25 7:09 ` Andreas Jaeger
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=hoof0wrfh9.fsf@byrd.suse.de \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).