public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52689] static linking with libstdc++ fails
Date: Sat, 24 Mar 2012 20:21:00 -0000	[thread overview]
Message-ID: <bug-52689-4-DY5F3e8Epk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52689-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52689

--- Comment #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-03-24 20:20:54 UTC ---
It looks like a linker bug.
I was able to reproduce the issue with Fedora17.

 $ ld -v
GNU ld version 2.22.52.0.1-10.fc17 20120131
 $ g++ x.cc -static-libstdc++
/usr/bin/ld: a.out: No symbol version section for versioned symbol
`_ZSt15future_category@@GLIBCXX_3.4.14'
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status

Gold is fine:

 $ sudo ln -f /bin/ld.gold /bin/ld
 $ g++ x.cc -static-libstdc++
 $


  parent reply	other threads:[~2012-03-24 20:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 17:31 [Bug libstdc++/52689] New: " jens.maurer at gmx dot net
2012-03-23 17:32 ` [Bug libstdc++/52689] " markus at trippelsdorf dot de
2012-03-23 20:14 ` jens.maurer at gmx dot net
2012-03-23 20:21 ` jens.maurer at gmx dot net
2012-03-23 21:19 ` markus at trippelsdorf dot de
2012-03-24 20:21 ` markus at trippelsdorf dot de [this message]
2012-03-27  7:32 ` jens.maurer at gmx dot net
2012-03-27  7:35 ` markus at trippelsdorf dot de
2012-03-27 15:37 ` jakub at gcc dot gnu.org
2012-03-29  6:36 ` bkoz at gcc dot gnu.org
2012-03-30 17:24 ` ro at gcc dot gnu.org
2012-04-03  8:01 ` ubizjak at gmail dot com
2012-04-03  8:57 ` ubizjak at gmail dot com
2012-04-03  9:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-04-04 17:06 ` bkoz at gcc dot gnu.org
2012-04-04 17:24 ` bkoz at gcc dot gnu.org
2012-04-04 17:27 ` uros at gcc dot gnu.org
2012-04-17  0:20 ` bkoz at gcc dot gnu.org
2012-04-17  2:23 ` bkoz at gcc dot gnu.org
2012-04-25  1:18 ` bkoz at gcc dot gnu.org
2012-04-25  2:01 ` bkoz at gcc dot gnu.org
2012-04-25 22:48 ` bkoz at gcc dot gnu.org
2012-05-02 22:44 ` bkoz at gcc dot gnu.org
2012-06-15 10:39 ` redi 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-52689-4-DY5F3e8Epk@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).