From: Harry Putnam <reader@newsguy.com>
To: help-gnu-emacs@gnu.org
Subject: gcc failure just like live bug 225705
Date: Thu, 13 Nov 2008 11:06:37 -0600 [thread overview]
Message-ID: <87k5b7lfmq.fsf@newsguy.com> (raw)
My failure appears to be like a current bug:
http://bugs.gentoo.org/show_bug.cgi?id=225705
Only that was on amd64 hardware and I'm on 32 bit intel.
That bug is about gcc-4.3.1 and my failure is gcc-4.3.2
Should I submit a new bug since its a different (higher) version of
that bug or just add comments to it?
Is there progress on this or some workaround?
partial emerge output below:
=====================================================
[...]
linux-gnu/bin/ -c -O2 -march=i686 -pipe -fprofile-generate -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wno-error -DHAVE_CONFIG_H -I. -Itreelang -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/treelang -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/../libdecnumber -I/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/../libdecnumber/bid -I../libdecnumber treelang/parse.c -o tr
eelang/parse.o
/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/treelang/parse.y: In function 'yyparse':
/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/treelang/parse.y:689: error: expected ';' before '}' token
/var/tmp/portage/sys-devel/gcc-4.3.2/work/gcc-4.3.2/gcc/treelang/parse.y:690: error: expected ';' before '}' token
make[3]: *** [treelang/parse.o] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/gcc'
make[2]: *** [all-stageprofile-gcc] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
make[1]: *** [stageprofile-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
make: *** [profiledbootstrap] Error 2
*
* ERROR: sys-devel/gcc-4.3.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 4616: Called toolchain_src_compile
* environment, line 5132: Called gcc_src_compile
* environment, line 2978: Called gcc_do_make
* environment, line 2801: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
* The die message:
* emake failed with profiledbootstrap
>>> Failed to emerge sys-devel/gcc-4.3.2, Log file:
>>> '/var/tmp/portage/sys-devel/gcc-4.3.2/temp/build.log'
[...]
next reply other threads:[~2008-11-13 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 17:06 Harry Putnam [this message]
2008-11-13 19:35 ` gcc failure just like live bug 225705 Tassilo Horn
2008-11-14 17:08 ` Harry Putnam
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5b7lfmq.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=help-gnu-emacs@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).