From: Roland McGrath <roland@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: LD_ASSUME_KERNEL problem
Date: Wed, 25 Jun 2003 06:11:00 -0000 [thread overview]
Message-ID: <200306250534.h5P5YP228238@magilla.sf.frob.com> (raw)
In-Reply-To: Andreas Jaeger's message of Tuesday, 17 June 2003 15:38:42 +0200 <hoof0wrfh9.fsf@byrd.suse.de>
> So, what can we do? We need a better way IMO to switch libraries to
> not affect all installed glibcs. Any good ideas?
Do you have a suggestion? For the path elements that come from the hwcap
list, you can exercise some control with LD_HWCAP_MASK. "i686" comes from
dl_platform, i.e. AT_PLATFORM. An override for that in glibc would have
the same issue, though you could override it in the kernel somehow specific
to 32-bit processes. We could add something like LD_EXCLUDE_PLATFORM to
give platform/hwcap strings that should not be put into the search list
when they normally would (then you could use that for "tls" as well).
next prev parent reply other threads:[~2003-06-25 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 13:38 Andreas Jaeger
2003-06-25 6:11 ` Roland McGrath [this message]
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=200306250534.h5P5YP228238@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=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).