public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53675] [4.8 Regression] bootstrap fails on non-TLS targets with multiple definitions of libstdc++ symbols
Date: Wed, 04 Jul 2012 09:23:00 -0000	[thread overview]
Message-ID: <bug-53675-4-mh0XPqTtOh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53675-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-04 09:22:58 UTC ---
I'm still seeing junk dwarf info:

/usr/bin/ld: Dwarf Error: found dwarf version '0', this reader only handles
version 2 and 3 information.
2.cc:(.text._Z6test01v+0x73): undefined reference to
`std::chrono::steady_clock::now()'
/usr/bin/ld: Dwarf Error: found dwarf version '12425', this reader only handles
version 2 and 3 information.
2.cc:(.text._Z6test01v+0xe1): undefined reference to
`std::chrono::steady_clock::now()'
collect2: error: ld returned 1 exit status

Will investigate ...


      parent reply	other threads:[~2012-07-04  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 21:07 [Bug bootstrap/53675] New: [4.8 Regression] bootstrap fails on netbsd5.1 due to unsupported dwarf4 info redi at gcc dot gnu.org
2012-06-15  8:30 ` [Bug bootstrap/53675] " rguenth at gcc dot gnu.org
2012-06-15 19:43 ` redi at gcc dot gnu.org
2012-06-16 13:22 ` [Bug bootstrap/53675] [4.8 Regression] bootstrap fails on netbsd5.1 with multiple definitions of libstdc++ symbols redi at gcc dot gnu.org
2012-06-18 17:36 ` [Bug bootstrap/53675] [4.8 Regression] bootstrap fails on non-TLS targets " redi at gcc dot gnu.org
2012-06-18 20:17 ` redi at gcc dot gnu.org
2012-07-03 20:55 ` redi at gcc dot gnu.org
2012-07-04  9:23 ` redi at gcc dot gnu.org [this message]

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-53675-4-mh0XPqTtOh@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).