public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/50349] /usr/bin/ld: warning: wildcard match appears in both version 'GLIBCXX_3.4' and 'CXXABI_1.3' in script
Date: Thu, 16 Feb 2012 23:13:00 -0000 [thread overview]
Message-ID: <bug-50349-4-jCyl7G4WMX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50349-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50349
--- Comment #3 from Pawel Sikora <pluto at agmk dot net> 2012-02-16 23:10:34 UTC ---
(In reply to comment #1)
> I am unable to reproduce this on F16,
>
> GNU ld version 2.21.53.0.1-6.fc16 20110716
> Copyright 2011 Free Software Foundation, Inc.
>
> Can you give me some more information about your ld, and include any special
> flags used to get the warnings. Thanks.
you need to use ld-gold for gcc build and configure gcc with
--enable-symvers=gnu.
the problem is in the libstdc++-v3/config/abi/pre/gnu.ver:
grep shows duplicated lines:
gnu.ver: _ZNKSs11_M_disjunctEPKc;
gnu.ver: _ZNKSbIwSt11char_traitsIwESaIwEE11_M_disjunctEPKw;
gnu.ver: _ZNKSs11_M_disjunctEPKc;
gnu.ver: _ZNKSbIwSt11char_traitsIwESaIwEE11_M_disjunctEPKw;
full build log attached.
next prev parent reply other threads:[~2012-02-16 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 19:44 [Bug libstdc++/50349] New: " pluto at agmk dot net
2012-02-16 21:05 ` [Bug libstdc++/50349] " bkoz at gcc dot gnu.org
2012-02-16 23:13 ` pluto at agmk dot net [this message]
2012-02-16 23:16 ` pluto at agmk dot net
2012-02-21 20:10 ` bkoz at gcc dot gnu.org
2012-02-21 23:50 ` bkoz at gcc dot gnu.org
2012-02-21 23:52 ` bkoz at gcc dot gnu.org
2012-02-24 20:35 ` bkoz 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-50349-4-jCyl7G4WMX@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).