gcc failure just like live bug 225705

gcc failure just like live bug 225705

[Harry Putnam]

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'

[...]

Re: gcc failure just like live bug 225705

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry?

> That bug is about gcc-4.3.1 and my failure is gcc-4.3.2

I don't see the relationship with emacs?  Wrong group?

Bye,
Tassilo

Re: gcc failure just like live bug 225705

[Harry Putnam]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry?
>
>> That bug is about gcc-4.3.1 and my failure is gcc-4.3.2
>
> I don't see the relationship with emacs?  Wrong group?

Gack, whoops.. Sorry. Yes.. I wondered why it hadn't shown up in
gmane.linux.gentoo.user.