public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/65522] [5 Regression] Svn revision 221590 fails bootstrap - ../libiberty/libiberty.a(cplus-dem.o): In function `ada_demangle': cplus-dem.c:(.text+0xdb8): multiple definition of `ada_demangle' ada/adadecode.o:adadecode.c:(.text+0x863): first defined here Date: Mon, 23 Mar 2015 15:00:00 -0000 [thread overview] Message-ID: <bug-65522-4-vhX4cn0Hsk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65522-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65522 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #35109|0 |1 is obsolete| | Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 35112 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35112&action=edit gcc5-pr65522.patch I'm actually testing a slightly adjusted variant that keeps the compatibility ada_demangle in libgnat* for ABI reasons, but not in gnat1 which doesn't use it and thus can link against libiberty.
next prev parent reply other threads:[~2015-03-23 14:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65522-4@http.gcc.gnu.org/bugzilla/> 2015-03-23 12:48 ` rguenth at gcc dot gnu.org 2015-03-23 13:02 ` jakub at gcc dot gnu.org 2015-03-23 13:44 ` jakub at gcc dot gnu.org 2015-03-23 13:49 ` jakub at gcc dot gnu.org 2015-03-23 13:51 ` ebotcazou at gcc dot gnu.org 2015-03-23 15:00 ` jakub at gcc dot gnu.org [this message] 2015-03-23 16:17 ` jakub at gcc dot gnu.org 2015-03-23 16:39 ` jakub 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-65522-4-vhX4cn0Hsk@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: linkBe 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).