sys-devel/binutils-2.19.50.0.1 fails to emerge during bootstrapping. The platform is SUSE 10 Enterprise SP 1. I have compared package versions against a successful bootstrapping done 24 hours earlier and I found these changes: < var/db/pkg/app-shells/bash-3.2_p48 --- > var/db/pkg/app-shells/bash-3.2_p17-r1 < var/db/pkg/sys-devel/bison-2.4.1 --- > var/db/pkg/sys-devel/bison-2.4-r1 The last part of the console log goes: gcc -DHAVE_CONFIG_H -I. -I/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils -I. -I. -I/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils -I../bfd -I/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils/../bfd -I/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils/../include -DLOCALEDIR="\"/local/tmp/s/usr/share/binutils-data/i686-pc-linux-gnu/2.19.50.0.1/locale\"" -Dbin_dummy_emulation=bin_vanilla_emulation -I/local/tmp/s/usr/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -O2 -march=i686 -pipe -c /local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils/rdcoff.c /bin/sh /local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils/../ylwrap /local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/binutils-2.19.50.0.1/binutils/arparse.y y.tab.c arparse.c y.tab.h arparse.h y.output arparse.output -- bison -y -d /local/tmp/s/usr/share/bison/c-skel.m4:19: error: m4_popdef: undefined macro: _m4_step /local/tmp/s/usr/share/bison/c-skel.m4:19: the top level bison: subsidiary program `m4' failed (exit status 1) make[4]: *** [arparse.c] Error 1 make[4]: *** Waiting for unfinished jobs.... /bin/sh ./libtool --tag=CC --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -O2 -march=i686 -pipe -L/local/tmp/s/usr/lib -R/local/tmp/s/usr/lib -L/local/tmp/s/lib -R/local/tmp/s/lib -o as-new app.o as.o atof-generic.o cond.o depend.o dwarf2dbg.o dw2gencfi.o ecoff.o ehopt.o expr.o flonum-copy.o flonum-konst.o flonum-mult.o frags.o hash.o input-file.o input-scrub.o listing.o literal.o macro.o messages.o output-file.o read.o remap.o sb.o stabs.o subsegs.o symbols.o write.o tc-i386.o obj-elf.o atof-ieee.o ../opcodes/libopcodes.la ../bfd/libbfd.la ../libiberty/libiberty.a make[4]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/binutils' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/binutils' make[2]: *** [all] Error 2 make[2]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/binutils' make[1]: *** [all-binutils] Error 2 libtool: link: gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -O2 -march=i686 -pipe -o .libs/as-new app.o as.o atof-generic.o cond.o depend.o dwarf2dbg.o dw2gencfi.o ecoff.o ehopt.o expr.o flonum-copy.o flonum-konst.o flonum-mult.o frags.o hash.o input-file.o input-scrub.o listing.o literal.o macro.o messages.o output-file.o read.o remap.o sb.o stabs.o subsegs.o symbols.o write.o tc-i386.o obj-elf.o atof-ieee.o -L/local/tmp/s/usr/lib -L/local/tmp/s/lib ../opcodes/.libs/libopcodes.so ../bfd/.libs/libbfd.so -L/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/libiberty/pic -liberty -lz ../libiberty/libiberty.a -Wl,-rpath -Wl,/local/tmp/s/usr/lib/binutils/i686-pc-linux-gnu/2.19.50.0.1 -Wl,-rpath -Wl,/local/tmp/s/usr/lib -Wl,-rpath -Wl,/local/tmp/s/lib make[4]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/gas' make[3]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/gas' make[2]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build/gas' make[1]: Leaving directory `/local/scratch/portage/sys-devel/binutils-2.19.50.0.1/work/build' make: *** [all] Error 2 * ERROR: sys-devel/binutils-2.19.50.0.1 failed: * emake failed
Don't know why, but since 2009-02-06 sys-devel/binutils-2.19.50.0.1 again emerges fine. I will keep console logs for about 7 days if anyone wants to investigate.
(In reply to comment #1) > Don't know why, but since 2009-02-06 sys-devel/binutils-2.19.50.0.1 again > emerges fine. I will keep console logs for about 7 days if anyone wants to > investigate. > Appreciate your work. Not sure what to do here so I'm resolving it as INVALID.
