public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "heroxbd at sohu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/52556] Ability to change GLIBC_DYNAMIC_LINKER
Date: Sat, 17 Aug 2013 11:40:00 -0000	[thread overview]
Message-ID: <bug-52556-4-r5ClLDv0qz@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

Benda Xu <heroxbd at sohu dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |heroxbd at sohu dot com

--- Comment #4 from Benda Xu <heroxbd at sohu dot com> ---
(In reply to Jakub Jelinek from comment #2)
> Just use -Wl,-dynamic-linker=/whatever/ld.so 

-Wl,-dynamic-linker=/whatever/ld.so cannot be set permanently. It requires a
wrapper to inject such argument all the time, which is ugly.

> or you could use --with-specs configure option.

Builtin specs of GCC is already very complicated (output from gcc-4.7.3
-dumpspecs on amd64):

...

*link:
%{!static:--eh-frame-hdr} %{m32|mx32:;:-m elf_x86_64}                   
%{m32:-m elf_i386}                    %{mx32:-m elf32_x86_64}  
%{shared:-shared}   %{!shared:     %{!static:       %{rdynamic:-export-dynamic}
      %{m32:-dynamic-linker
%{muclibc:/lib/ld-uClibc.so.0;:%{mbionic:/system/bin/linker;:/lib/ld-linux.so.2}}}
      %{m32|mx32:;:-dynamic-linker
%{muclibc:/lib/ld64-uClibc.so.0;:%{mbionic:/system/bin/linker64;:/lib64/ld-linux-x86-64.so.2}}}
      %{mx32:-dynamic-linker
%{muclibc:/lib/ldx32-uClibc.so.0;:%{mbionic:/system/bin/linkerx32;:/libx32/ld-linux-x32.so.2}}}}
    %{static:-static}}

...

writing an equivalent specs with prefixed dynamic linker is horrible.

Please consider sopport dynamic linker prefix by an extra configure option.


  parent reply	other threads:[~2013-08-17 11:40 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 [this message]
2013-08-18  7:19 ` heroxbd at sohu dot com
2014-03-19 23:19 ` brooks at gcc dot gnu.org
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-r5ClLDv0qz@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).