Building from a combined tree of gcc and binutils using gcc-2.95.2,
I get this error with "Fri Jan 14 01:28:39 UTC 2005" (no configure
arguments, build gcc is gcc-2.95.2, ld used by bootstrap-gcc is
/usr/ccs/bin/ld, as used by bootstrap-gcc is /usr/ccs/bin/as):
gcc -DHAVE_CONFIG_H -I. -I/tmp/hptmp/combined/binutils -I. -D_GNU_SOURCE -I.
-I/tmp/hptmp/combined/binutils -I../bfd -I/tmp/hptmp\
-I/tmp/hptmp/combined/binutils/../intl -I../intl -DLOCALEDIR=\
"\"/usr/local/share/locale\"" -Dbin_dummy_emulation=bin_vanilla_emulation -W
-Wall -Wstrict-prototypes -Wmissing-prototypes -g \
-O2 -c /tmp/hptmp/combined/binutils/filemode.c
/bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -g -O2 -o size size.o bucomm.o version.o f\
ilemode.o ../bfd/libbfd.la ../libiberty/libiberty.a
gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -o size size.o
bucomm.o version.o filemode.o ../bfd/.libs/libbfd.a \
Undefined first referenced
symbol in file
ld: fatal: Symbol referencing errors. No output written to size
collect2: ld returned 1 exit status
make: *** [size] Error 1
make: Leaving directory `/tmp/hptmp/obj/binutils'
Yes, this is the binutils build breaking, but building binutils
*by itself* succeeds. It seems that the "intl" subdir component
of gcc is at fault. I recall it has been this way for a long time.
Usually --disable-nls helps, but see also binutils PR 673.
This is a dup of bug 11074. The problem is related to how the build is picking up the wrong headers.
*** This bug has been marked as a duplicate of 11074 ***
(In reply to comment #1)
> This is a dup of bug 11074. The problem is related to how the build is
picking up the wrong headers.
> *** This bug has been marked as a duplicate of 11074 ***
Actually, it's not really a duplicate of bug 11074 at all, although they have
the same symptoms. In this case, all the right configury is in place, but the
binutils makefiles don't always specify @INTLLIBS@ when linking.
In 11074, adding @INTLLIBS@ is pointless because it also lacks the gettext
macros that would normally provide @INTLLIBS@.
In any case, it is not a gcc bug, but a binutils one - it's their Makefiles that
Reopened as it's not a duplicate... (wait for it)
...and closed as invalid, as this is a binutils bug. See comment #2.