Package: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of libv8 on armel are now failing because its build system
insists for some reason on passing the unsupported -m32 flag:
make[2]: Entering directory `/.../libv8-3.5.10.24/out'
g++ '-DENABLE_DEBUGGER_SUPPORT' '-DV8_TARGET_ARCH_ARM'
'-DCAN_USE_VFP_INSTRUCTIONS' '-DUSE_EABI_HARDFLOAT=0' -I../src -Wall -Werror -W
-Wno-unused-parameter -Wnon-virtual-dtor -pthread -fno-rtti -fno-exceptions
-pedantic -m32 -ansi -fvisibility=hidden -fPIC -fdata-sections
-ffunction-sections -fomit-frame-pointer -O3 -MMD -MF
/.../libv8-3.5.10.24/out/arm.release/.deps//.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o.d.raw
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -Wall -Wno-psabi -c -o
/.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o
../src/allocation.cc
cc1plus: error: unrecognized command line option '-m32'
make[2]: ***
[/.../libv8-3.5.10.24/out/arm.release/obj.target/preparser_lib/src/allocation.o]
Error 1
make[1]: *** [arm.release] Error 2
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
(Incidentally, the -MF option's argument looks bogus as well; GCC
doesn't appear to care about that at the moment, though.)
Could you please take a look?
Thanks!
_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
