public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59122] [4.9 Regression] libsanitizer merge from upstream r191666 causes duplicate symbol errors
Date: Thu, 14 Nov 2013 17:23:00 -0000 [thread overview]
Message-ID: <bug-59122-4-ydK6CCrUIj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59122-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59122
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #2)
> (In reply to Jakub Jelinek from comment #1)
> > This seems to work for me in the cross, but it is a hack in any case (before
> > and now with the patch).
>
> I'll give your patch a try, thanks.
Your patch fixed the duplicate symbol errors for me, so unless someone else has
a better idea, I'm fine with it.
next prev parent reply other threads:[~2013-11-14 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 22:53 [Bug sanitizer/59122] New: " bergner at gcc dot gnu.org
2013-11-13 23:10 ` [Bug sanitizer/59122] " jakub at gcc dot gnu.org
2013-11-14 9:51 ` [Bug sanitizer/59122] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-11-14 15:29 ` bergner at gcc dot gnu.org
2013-11-14 17:23 ` bergner at gcc dot gnu.org [this message]
2013-11-14 18:28 ` jakub at gcc dot gnu.org
2013-11-15 16:58 ` bergner 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-59122-4-ydK6CCrUIj@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).