On Mon, Oct 21, 2013 at 6:01 AM, <daniel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > I am trying to build gcc 4.8.2, and I got following compilation error: > > make[3]: Entering directory `[path]/gcc/obj/gcc' > g++ -g -fkeep-inline-functions -DIN_GCC -fno-exceptions -fno-rtti > -fasynchronous-unwind-tables -W -Wall -Wwrite-strings -Wcast-qual > -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros > -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o > build/genconstants \ > build/genconstants.o build/read-md.o build/errors.o > ../build-x86_64-unknown-linux-gnu/libiberty/libiberty.a > build/genconstants ../../gcc-4.8.2/gcc/config/i386/i386.md \ > > tmp-constants.h > /bin/sh ../../gcc-4.8.2/gcc/../move-if-change tmp-constants.h > insn-constants.h > echo timestamp > s-constants > g++ -g -fkeep-inline-functions -DIN_GCC -fno-exceptions -fno-rtti > -fasynchronous-unwind-tables -W -Wall -Wwrite-strings -Wcast-qual > -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros > -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o > build/gengtype \ > build/gengtype.o build/errors.o build/gengtype-lex.o > build/gengtype-parse.o build/gengtype-state.o build/version.o > ../build-x86_64-unknown-linux-gnu/libiberty/libiberty.a > build/gengtype.o: In function `double_int::operator*=(double_int)': > [path]/gcc/obj/gcc/../../gcc-4.8.2/gcc/double-int.h:263: undefined reference > to `double_int::operator*(double_int) const' > build/gengtype.o: In function `double_int::operator+=(double_int)': > [path]/gcc/obj/gcc/../../gcc-4.8.2/gcc/double-int.h:270: undefined reference > to `double_int::operator+(double_int) const' > build/gengtype.o: In function `double_int::operator-=(double_int)': > [path]/gcc/obj/gcc/../../gcc-4.8.2/gcc/double-int.h:277: undefined reference > to `double_int::operator-(double_int) const' > collect2: ld returned 1 exit status > make[3]: *** [build/gengtype] Error 1 > make[3]: Leaving directory `[path]/gcc/obj/gcc' Please file a bug report at http://gcc.gnu.org/bugzilla/ . Sorry about the problem--looks like some issue with building with current GCC with GCC 4.4. Ian
