public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51026] New: Bootstrap failure due to libstdc++ on x86_64-darwin11
Date: Tue, 08 Nov 2011 08:06:00 -0000	[thread overview]
Message-ID: <bug-51026-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51026
           Summary: Bootstrap failure due to libstdc++ on x86_64-darwin11
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: blocker
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: fxcoudert@gcc.gnu.org
                CC: amacleod@redhat.com
              Host: x86_64-apple-darwin11
            Target: x86_64-apple-darwin11
             Build: x86_64-apple-darwin11


Bootstrap currently fails on x86_64-apple-darwin11 due to a problem in building
libstdc++.6.dylib:

ld: duplicate symbol std::atomic_thread_fence(std::memory_order) in
.libs/functexcept.o and .libs/compatibility-atomic-c++0x.o for architecture
x86_64
collect2: error: ld returned 1 exit status
make[5]: *** [libstdc++.la] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-stage1-target-libstdc++-v3] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [all] Error 2


             reply	other threads:[~2011-11-08  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  8:06 fxcoudert at gcc dot gnu.org [this message]
2011-11-08  8:11 ` [Bug libstdc++/51026] " fxcoudert at gcc dot gnu.org
2011-11-08 10:11 ` [Bug libstdc++/51026] [4.7 Regression] " burnus at gcc dot gnu.org
2011-11-08 13:42 ` amacleod at redhat dot com
2011-11-09 10:11 ` fxcoudert 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-51026-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).