Bug#650548: marked as done (libv8: FTBFS on armel: unrecognized option -m32)
Your message dated Fri, 02 Dec 2011 11:19:58 + with message-id e1rwr9q-0002ia...@franck.debian.org and subject line Bug#650548: fixed in libv8 3.5.10.24-3 has caused the Debian Bug report #650548, regarding libv8: FTBFS on armel: unrecognized option -m32 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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! ---End Message--- ---BeginMessage--- Source: libv8 Source-Version: 3.5.10.24-3 We believe that the bug you reported is fixed in the latest version of libv8, which is due to be installed in the Debian FTP archive: libv8-3.5.10.24_3.5.10.24-3_amd64.deb to main/libv/libv8/libv8-3.5.10.24_3.5.10.24-3_amd64.deb libv8-dbg_3.5.10.24-3_amd64.deb to main/libv/libv8/libv8-dbg_3.5.10.24-3_amd64.deb libv8-dev_3.5.10.24-3_amd64.deb to main/libv/libv8/libv8-dev_3.5.10.24-3_amd64.deb libv8_3.5.10.24-3.debian.tar.gz to main/libv/libv8/libv8_3.5.10.24-3.debian.tar.gz libv8_3.5.10.24-3.dsc to main/libv/libv8/libv8_3.5.10.24-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal kapo...@melix.org (supplier of updated libv8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 02 Dec 2011 10:17:48 +0100 Source: libv8 Binary: libv8-dev libv8-3.5.10.24 libv8-dbg Architecture: source amd64 Version: 3.5.10.24-3 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Jérémy Lal kapo...@melix.org Description: libv8-3.5.10.24 - v8 JavaScript engine - runtime library libv8-dbg - v8 JavaScript engine - debugging symbols libv8-dev - v8 JavaScript engine - development files Closes: 650548 Changes: libv8 (3.5.10.24-3) unstable; urgency=low . * Fix build failures for arm: + arm_neon=0 for armhf + vfp3=off for armel Closes: bug#650548 Checksums-Sha1: ab57477637328c0ea8b0c423d82d368c492832ba 1504 libv8_3.5.10.24-3.dsc 07ac27330d0320ee47526c52d2937134e0f51f25 25950 libv8_3.5.10.24-3.debian.tar.gz 09c01a71f48c4df6731795dcd723a178dbeaf349 80704 libv8-dev_3.5.10.24-3_amd64.deb bfbde56da748663bb5669cef296210dd69760148 1414410 libv8-3.5.10.24_3.5.10.24-3_amd64.deb 5035488c41a5be5b8278f542acaa94854a81 24568098 libv8-dbg_3.5.10.24-3_amd64.deb Checksums-Sha256: b2512e70728a5e639a5e0a7c25343119638444c6db2e5b376c3e2ba0853b66e1 1504 libv8_3.5.10.24-3.dsc e90109e6888d2d6a49f88bd57458852bc21ed53094425b14c169f676e26a4315 25950 libv8_3.5.10.24-3.debian.tar.gz c876ebc7e28a800a2c741a157161dc4cf5d85c8e411404fe13a34bdde01a7a68
Bug#650548: marked as done (libv8: FTBFS on armel: unrecognized option -m32)
Your message dated Thu, 01 Dec 2011 23:39:26 + with message-id e1rwgdu-0004hd...@franck.debian.org and subject line Bug#650548: fixed in libv8 3.5.10.24-2 has caused the Debian Bug report #650548, regarding libv8: FTBFS on armel: unrecognized option -m32 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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! ---End Message--- ---BeginMessage--- Source: libv8 Source-Version: 3.5.10.24-2 We believe that the bug you reported is fixed in the latest version of libv8, which is due to be installed in the Debian FTP archive: libv8-3.5.10.24_3.5.10.24-2_amd64.deb to main/libv/libv8/libv8-3.5.10.24_3.5.10.24-2_amd64.deb libv8-dbg_3.5.10.24-2_amd64.deb to main/libv/libv8/libv8-dbg_3.5.10.24-2_amd64.deb libv8-dev_3.5.10.24-2_amd64.deb to main/libv/libv8/libv8-dev_3.5.10.24-2_amd64.deb libv8_3.5.10.24-2.debian.tar.gz to main/libv/libv8/libv8_3.5.10.24-2.debian.tar.gz libv8_3.5.10.24-2.dsc to main/libv/libv8/libv8_3.5.10.24-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal kapo...@melix.org (supplier of updated libv8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 01 Dec 2011 14:31:59 +0100 Source: libv8 Binary: libv8-dev libv8-3.5.10.24 libv8-dbg Architecture: source amd64 Version: 3.5.10.24-2 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Jérémy Lal kapo...@melix.org Description: libv8-3.5.10.24 - v8 JavaScript engine - runtime library libv8-dbg - v8 JavaScript engine - debugging symbols libv8-dev - v8 JavaScript engine - development files Closes: 650547 650548 650549 Changes: libv8 (3.5.10.24-2) unstable; urgency=low . * Set -Wno-unused-but-set-variable, i386 build fail otherwise. Closes: bug#650547 * Remove mipsel from architectures. Will be re-enabled when upstream really supports it. Closes: bug#650549 * Disable default arm flags (debian/0014_disable_armv7_defaults.patch) and set them properly for armel and armhf, using GYPFLAGS variable in debian/rules. Closes: bug#650548 * Remove 0009_unaligned_access_armel.patch, never proved it was needed. * Remove -fvisibility=hidden flag, applied upstream. * CCFLAGS are ignored by the build system, use CXXFLAGS instead. Checksums-Sha1: 0ac3806693a88a2cf2f8f1df996ee4b03df96c93 1504 libv8_3.5.10.24-2.dsc 1ee2e9fc01a24866f2676ef83542a59b6e1c87d0 25766 libv8_3.5.10.24-2.debian.tar.gz
