[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

GCC failure in k3d autobuilding.

	Hello, fellow developers. I have found this log in elara (the ARM buildd):

source='measurement.cpp' object='measurement.lo' libtool=yes \
depfile='.deps/measurement.Plo' tmpdepfile='.deps/measurement.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile arm-linux-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"k3d\" -DVERSION=\"0.4.0.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAPY_HAVE_NUMERIC_LIMITS=1 -DHAPY_HAVE_STD_ITERATOR_TYPE=1  -I. -I.  -I.. -I../boost -I/usr/lib/sigc++-1.0/include -I/usr/include/sigc++-1.0 -DK3D_OLD_SIGC_HEADERS=1   -Wall -Wno-ctor-dtor-privacy -g -O2 -c -o measurement.lo `test -f measurement.cpp || echo './'`measurement.cpp
arm-linux-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"k3d\" -DVERSION=\"0.4.0.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAPY_HAVE_NUMERIC_LIMITS=1 -DHAPY_HAVE_STD_ITERATOR_TYPE=1 -I. -I. -I.. -I../boost -I/usr/lib/sigc++-1.0/include -I/usr/include/sigc++-1.0 -DK3D_OLD_SIGC_HEADERS=1 -Wall -Wno-ctor-dtor-privacy -g -O2 -c measurement.cpp -MT measurement.lo -MD -MP -MF .deps/measurement.TPlo  -fPIC -DPIC
arm-linux-g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.

	You can see the full build log in

http://buildd.debian.org/fetch.php?&pkg=k3d&ver=0.4.0.0-2&arch=arm&stamp=1088976206&file=log&as=raw

	Should I take care of that? Is it transitory, or is a GCC bug?

	I would have expected an ICE message, not a Killed one.

	Thanks in advance,


		Ender.	
-- 
Network engineer
Debian Developer
Reply to: