public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ludo at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65711] New: arm*-linux* "link" spec passes '-dynamic-linker' even for '-shared'
Date: Thu, 09 Apr 2015 08:03:00 -0000	[thread overview]
Message-ID: <bug-65711-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65711

            Bug ID: 65711
           Summary: arm*-linux* "link" spec passes '-dynamic-linker' even
                    for '-shared'
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ludo at gnu dot org

gcc/config/arm/linux-elf.h defines LINUX_TARGET_LINK_SPEC to (simplified):

  %{!static -dynamic-linker LINKER}

However, '-dynamic-linker' should not be passed when '-shared' is used.  The
correct way appears to be what config/i386/gnu-user.h does, which is:

  %{!static %{!shared -dynamic-linker LINKER}}

I believe the attached patch fixes that.  At least both 4.8.4 and 4.9.2 are
affected.

(Initially discussed in the context of <http://bugs.gnu.org/20102>.)


             reply	other threads:[~2015-04-09  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  8:03 ludo at gnu dot org [this message]
2015-04-09  8:04 ` [Bug target/65711] " ludo at gnu dot org
2015-06-23  9:07 ` ludo at gcc dot gnu.org
2015-06-23  9:16 ` ludo at gcc dot gnu.org
2015-06-23  9:22 ` ludo at gcc dot gnu.org
2015-06-23  9:27 ` ludo at gcc dot gnu.org
2015-06-26  7:54 ` ramana at gcc dot gnu.org
2015-07-24 14:28 ` nsz at gcc dot gnu.org
2015-07-24 16:01 ` nsz at gcc dot gnu.org
2015-07-24 16:13 ` nsz 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-65711-4@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).