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 ada/30684] [4.2 regression] boostrap failed with undefined reference to system__pure_exceptions_* Date: Fri, 02 Feb 2007 23:25:00 -0000 [thread overview] Message-ID: <20070202232535.29804.qmail@sourceware.org> (raw) In-Reply-To: <bug-30684-7667@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pluto at agmk dot net 2007-02-02 23:25 ------- i don't know what's wrong. s-purex.o exports such symbols. linker bug? [builder2@fly ada]$ objdump -t s-purexc.o|grep system__pure_exceptions 0000000000000000 g F .text 0000000000000004 0x80 system__pure_exceptions__exception_typeIP 0000000000000004 g F .text 000000000000001c 0x88 system__pure_exceptions___elabs 0000000000000000 g O .sbss 0000000000000004 system__pure_exceptions_E [builder2@fly ada]$ objdump -t b_gnatb.o|grep system__pure_exceptions 0000000000000000 *UND* 0000000000000000 system__pure_exceptions___elabs 0000000000000000 *UND* 0000000000000000 system__pure_exceptions_E 0000000000000114 g O .sdata 0000000000000004 system__pure_exceptionsS -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30684
next prev parent reply other threads:[~2007-02-02 23:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-02 23:00 [Bug ada/30684] New: " pluto at agmk dot net 2007-02-02 23:25 ` pluto at agmk dot net [this message] 2007-02-03 17:32 ` [Bug ada/30684] " jsm28 at gcc dot gnu dot org 2007-02-18 13:25 ` ebotcazou at gcc dot gnu dot org 2007-02-19 18:10 ` ebotcazou at gcc dot gnu dot org 2007-02-19 21:03 ` mmitchel at gcc dot gnu dot org 2007-02-19 21:24 ` [Bug ada/30684] [4.1 " ebotcazou at gcc dot gnu dot org 2007-02-20 23:54 ` ebotcazou at gcc dot gnu dot org 2007-02-20 23:56 ` ebotcazou at gcc dot gnu dot 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=20070202232535.29804.qmail@sourceware.org \ --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).