public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brooks at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/52556] Ability to change GLIBC_DYNAMIC_LINKER
Date: Wed, 19 Mar 2014 23:19:00 -0000 [thread overview]
Message-ID: <bug-52556-4-mkqkoKZGSg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52556-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556
Brooks Moses <brooks at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brooks at gcc dot gnu.org
--- Comment #6 from Brooks Moses <brooks at gcc dot gnu.org> ---
Richard Biener mentioned that Red Hat has "a local patch that allows amending
link_spec from an external file, which would sound more flexible" here:
http://patchwork.ozlabs.org/patch/80538/
It's not completely clear whether it applies to this case, however; he
mentioned that it could be used to produce the equivalent of a -Wl,-rpath=...
option. The Google-branch change that Christer mentions adds a
-dynamic-linker=... option to the link spec rather than an -rpath option -- I
would guess that the patch Richard mentions could cover that as well, but I'm
not sure.
next prev parent reply other threads:[~2014-03-19 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 11:25 [Bug driver/52556] New: " christer.solskogen at gmail dot com
2012-03-11 12:55 ` [Bug driver/52556] " christer.solskogen at gmail dot com
2012-03-11 14:14 ` jakub at gcc dot gnu.org
2012-03-11 15:51 ` christer.solskogen at gmail dot com
2013-08-17 11:40 ` heroxbd at sohu dot com
2013-08-18 7:19 ` heroxbd at sohu dot com
2014-03-19 23:19 ` brooks at gcc dot gnu.org [this message]
2023-08-20 21:15 ` pinskia at gcc dot gnu.org
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=bug-52556-4-mkqkoKZGSg@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).