Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 246266 - sys-devel/gcc-4.3.2: build fail with sys-devel/bison-2.4
Summary: sys-devel/gcc-4.3.2: build fail with sys-devel/bison-2.4
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
: 241214 246358 246630 246841 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-10 11:18 UTC by Robson Roberto Souza Peixoto
Modified: 2009-04-14 01:59 UTC (History)
12 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
bison-2.4.1_pre20081111.patch (bison-2.4.1_pre20081111.patch,7.69 KB, patch)
2008-11-11 17:24 UTC, Peter Alfredsen (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Robson Roberto Souza Peixoto 2008-11-10 11:18:54 UTC
/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/./prev-gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/./prev-gcc/ -B/usr/i686-pc-linux-gnu/bin/ -c   -O2 -march=pentium-m -mtune=pentium-m -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 treelang/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] Erro 1
make[3]: Saindo do diretório `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/gcc'
make[2]: ** [all-stageprofile-gcc] Erro 2
make[2]: Saindo do diretório `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
make[1]: ** [stageprofile-bubble] Erro 2
make[1]: Saindo do diretório `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
make: ** [profiledbootstrap] Erro 2
 * 
 * ERROR: sys-devel/gcc-4.3.2 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called src_compile
 * environment, line 4574:  Called toolchain_src_compile
 * environment, line 5090:  Called gcc_src_compile
 * environment, line 2936:  Called gcc_do_make
 * environment, line 2759:  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
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.3.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.3.2/temp/environment'.
 * 


Reproducible: Always

Steps to Reproduce:
1. after bootstrap
2. env-update ; source /etc/profile ; etc-update
3. emerge system
Comment 1 Robson Roberto Souza Peixoto 2008-11-10 11:26:50 UTC
(In reply to comment #0)
> /var/tmp/portage/sys-devel/gcc-4.3.2/work/build/./prev-gcc/xgcc
> -B/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/./prev-gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -c   -O2 -march=pentium-m -mtune=pentium-m -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 treelang/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] Erro 1
> make[3]: Saindo do diretório
> `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build/gcc'
> make[2]: ** [all-stageprofile-gcc] Erro 2
> make[2]: Saindo do diretório `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
> make[1]: ** [stageprofile-bubble] Erro 2
> make[1]: Saindo do diretório `/var/tmp/portage/sys-devel/gcc-4.3.2/work/build'
> make: ** [profiledbootstrap] Erro 2
>  * 
>  * ERROR: sys-devel/gcc-4.3.2 failed.
>  * Call stack:
>  * ebuild.sh, line   49:  Called src_compile
>  * environment, line 4574:  Called toolchain_src_compile
>  * environment, line 5090:  Called gcc_src_compile
>  * environment, line 2936:  Called gcc_do_make
>  * environment, line 2759:  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
>  * 
>  * If you need support, post the topmost build error, and the call stack if
> relevant.
>  * A complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.3.2/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.3.2/temp/environment'.
>  * 
> 
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. after bootstrap
> 2. env-update ; source /etc/profile ; etc-update
> 3. emerge system
sorry
3. emerge -e system
> 

# emerge --info
Portage 2.2_rc13 (default/linux/x86/2008.0, gcc-4.3.2, glibc-2.8_p20080602-r0, 2.6.27-7-generic i686)
=================================================================
System uname: Linux-2.6.27-7-generic-i686-Intel-R-_Celeron-R-_M_CPU_420_@_1.60GHz-with-glibc2.0
Timestamp of tree: Mon, 10 Nov 2008 09:07:02 +0000
app-shells/bash:     3.2_p39
dev-lang/python:     2.5.2-r8
sys-apps/baselayout: 2.0.0
sys-apps/openrc:     0.3.0-r1
sys-apps/sandbox:    1.2.18.1-r3
sys-devel/autoconf:  2.63
sys-devel/automake:  1.10.1
sys-devel/binutils:  2.19
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="x86 ~x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium-m -mtune=pentium-m -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/gentoo-release /etc/terminfo"
CXXFLAGS="-O2 -march=pentium-m -mtune=pentium-m -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="pt_BR.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="pt_BR en_US"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="acl acpi alsa apic arch_perfmon berkdb bts bzip2 cdr clflush cli cmov constant_tsc cracklib crypt cups cx8 de dri dts dvd fpu fxsr gdbm gpm iconv ipv6 isdnlog mca mce midi mmx monitor msr mtrr mudflap ncurses nls nptl nptlonly nx openmp pae pam pat pbe pcre perl pge pni pppd pse python readline reflection sep session spl ss sse sse2 ssl sysfs tcpd tm tm2 tsc unicode up vme x86 xorg xtpr zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="pt_BR en_US" USERLAND="GNU" VIDEO_CARDS="fbdev glint i810 intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware voodoo"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

sys-devel/bison-2.4  USE="nls -static"


Comment 2 torindel 2008-11-10 16:59:19 UTC
Same here on ~amd64, gcc-4.3.2 doesn't compile with bison-2.4, and it doesn't have any problems with bison-2.3
Comment 3 Fabian Groffen gentoo-dev 2008-11-10 19:20:05 UTC
Ohw, so it IS a bison problem.  I guess we can mask in that case.  Thanks, I'll look into it.
Comment 4 Fabian Groffen gentoo-dev 2008-11-10 20:56:41 UTC
drobbins>
zmedico: I got a bug for you to assign to vapier
[9:53pm] <drobbins>
zmedico: http://bugs.gentoo.org/show_bug.cgi?id=246266
[9:53pm] <drobbins>
zmedico: it breaks ~amd64 and ~x86. bison 2.4 and gcc 4.3.2 don't like each other.
[9:53pm] <drobbins>
looks like vapier put it into unstable

not gentoo/alt only.
Comment 5 Fabian Groffen gentoo-dev 2008-11-10 20:59:33 UTC
Ccing base-system for bison-2.4
Comment 6 Wormo (RETIRED) gentoo-dev 2008-11-11 06:39:49 UTC
*** Bug 246358 has been marked as a duplicate of this bug. ***
Comment 7 Peter Alfredsen (RETIRED) gentoo-dev 2008-11-11 17:24:34 UTC
Created attachment 171440 [details, diff]
bison-2.4.1_pre20081111.patch

This is what upstream used to fix this with in their git repository.
Comment 8 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-11-12 16:53:18 UTC
I also found that gcc-4.2.4 fails in the same way as 4.3.2
Comment 9 Mark Loeser (RETIRED) gentoo-dev 2008-11-12 17:42:30 UTC
*** Bug 241214 has been marked as a duplicate of this bug. ***
Comment 10 Doug Goldstein (RETIRED) gentoo-dev 2008-11-12 18:50:41 UTC
This is fixed with a compat fix in bison-2.4-r1, however gcc should be updated for the change in syntax/defaults that appears to be happening in bison.
Comment 11 Leung Ki Chi 2008-11-13 00:51:58 UTC
(In reply to comment #10)
> This is fixed with a compat fix in bison-2.4-r1, however gcc should be updated
> for the change in syntax/defaults that appears to be happening in bison.
> 

Confirm that 2.4-r1 lets gcc compile once more.
Comment 12 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-11-13 17:25:59 UTC
*** Bug 246630 has been marked as a duplicate of this bug. ***
Comment 13 SpanKY gentoo-dev 2008-11-14 08:01:55 UTC
no need to change the code if bison is changing back and gcc upstream will eventually make their own changes ...
Comment 14 Jeroen Roovers (RETIRED) gentoo-dev 2008-11-17 06:54:10 UTC
*** Bug 246841 has been marked as a duplicate of this bug. ***
Comment 15 samLT 2009-04-13 20:18:21 UTC
same problem appear when upgrading gcc from 4.3.2 to 4.3.3:
sys-devel/gcc-4.3.3-r2 [4.3.2-r3]
 
I only se the beison-2.4-r1 ebuild on the cvs
http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/sys-devel/bison/bison-2.4-r1.ebuild

but not locally (after an emerge --sync), so what am I supposed to do?

I'm currently downgrading bison-2.4 to bison-2.3, but there may be a better way (e.g.: copying the bison-2.4-r1 ebuild in an overlay...) ?

Comment 16 samLT 2009-04-13 20:21:38 UTC
I meant bison-2.4.1 when everytime I said bison-2.4
Comment 17 samLT 2009-04-13 20:26:39 UTC
I'm really sorry for the flood, but actually this is almost the same bug, but with

gcc-4.3.3-r2 and bison-2.4.1, and *not* with bison-2.4 as I said before.

Should I open a new bug report for it?
Comment 18 SpanKY gentoo-dev 2009-04-14 01:59:56 UTC
file a new bug