public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mckelvey at maskull dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/15673] Errors in stage 3; genmodes.c Date: Mon, 31 May 2004 18:51:00 -0000 [thread overview] Message-ID: <20040530185230.2688.qmail@sourceware.org> (raw) In-Reply-To: <20040527054918.15673.mckelvey@maskull.com> ------- Additional Comments From mckelvey at maskull dot com 2004-05-30 18:52 ------- OK, what is the next step here? I refetched everything from CVS yesterday and it failed the same way. I am building in the recommended manner, in a separate empty directory, with approved configuration and build options that have worked for months in their present exact form. I don't know why -Werror is being set, but the main problem is that the size warnings point to something very basic. If I remove -Werror I can get genmodes and errors to compile, but then the link of genmodes fails thusly: stage2/xgcc -Bstage2/ -B/usr/local/alphaev56-unknown-linux-gnu/bin/ -O -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Werror -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o genmodes \ genmodes.o errors.o ../libiberty/libiberty.a stage2/crtbegin.o: In function `frame_dummy': stage2/crtbegin.o(.text+0x94): undefined reference to `_Jv_RegisterClasses' collect2: ld returned 1 exit status -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15673
next prev parent reply other threads:[~2004-05-30 18:52 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-27 18:16 [Bug bootstrap/15673] New: " mckelvey at maskull dot com 2004-05-27 19:18 ` [Bug bootstrap/15673] " falk at debian dot org 2004-05-27 20:30 ` pinskia at gcc dot gnu dot org 2004-05-28 1:45 ` mckelvey at maskull dot com 2004-05-28 1:58 ` falk at debian dot org 2004-05-28 2:01 ` mckelvey at maskull dot com 2004-05-28 16:02 ` mckelvey at maskull dot com 2004-05-31 18:51 ` mckelvey at maskull dot com [this message] 2004-05-31 18:57 ` pinskia at gcc dot gnu dot org 2004-05-31 21:24 ` mckelvey at maskull dot com 2004-05-31 21:32 ` pinskia at gcc dot gnu dot org 2004-06-01 1:02 ` mckelvey at maskull dot com 2004-06-01 1:04 ` pinskia at gcc dot gnu dot org 2004-06-04 5:25 ` mckelvey at maskull dot com 2004-06-04 5:28 ` pinskia 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=20040530185230.2688.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).