Bug#777971: librcsb-core-wrapper: ftbfs with GCC-5
Control: tags -1 + patch pending attaching patch, and uploading to delayed. diff -Nru librcsb-core-wrapper-1.005/debian/changelog librcsb-core-wrapper-1.005/debian/changelog --- librcsb-core-wrapper-1.005/debian/changelog 2015-02-14 18:08:44.0 +0100 +++ librcsb-core-wrapper-1.005/debian/changelog 2015-07-10 13:47:21.0 +0200 @@ -1,3 +1,9 @@ +librcsb-core-wrapper (1.005-3.1) unstable; urgency=medium + + * Fix GCC version detection. Closes: #777971. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 13:46:42 +0200 + librcsb-core-wrapper (1.005-3) unstable; urgency=medium * Patch for Henry Spencer regular expressions (regex) library contains diff -Nru librcsb-core-wrapper-1.005/debian/patches/gcc5.diff librcsb-core-wrapper-1.005/debian/patches/gcc5.diff --- librcsb-core-wrapper-1.005/debian/patches/gcc5.diff 1970-01-01 01:00:00.0 +0100 +++ librcsb-core-wrapper-1.005/debian/patches/gcc5.diff 2015-07-10 13:52:00.0 +0200 @@ -0,0 +1,13 @@ +Index: b/etc/platform.sh +=== +--- a/etc/platform.sh b/etc/platform.sh +@@ -67,7 +67,7 @@ case `uname -s` in + # Check if it is a Linux platform + Linux) + # Check if it is GCC version 4.x +- gcc_ver=`gcc --version | grep -e 4\.` ++ gcc_ver=`gcc --version | grep -e [456789]\.` + if [[ -z $gcc_ver ]] + then + # It is not GCC version 4.x. Check if it is GCC version 3.x diff -Nru librcsb-core-wrapper-1.005/debian/patches/series librcsb-core-wrapper-1.005/debian/patches/series --- librcsb-core-wrapper-1.005/debian/patches/series2015-02-14 17:44:47.0 +0100 +++ librcsb-core-wrapper-1.005/debian/patches/series2015-07-10 13:45:51.0 +0200 @@ -12,3 +12,4 @@ exit-in-shlib make_test_target regcomp_cert_fix.patch +gcc5.diff
Bug#777971: Please help porting Core Wrapper to gcc 5.0 (Was: Help with libtool needed (Was: Bug#777971: librcsb-core-wrapper: ftbfs with GCC-5))
Hi, as you might know the Core Wrapper library was packaged for Debian (initially by Laszlo Kajan for the Debian Med team). Debian is migrating to gcc-5 and it seems there are some hard to reproduce problems with libtool (see the full bug log here https://bugs.debian.org/777971) and a shell script (etc/platform.sh) that explicitly excludes gcc-5. Do you plan any upgrade of the library to anable gcc-5 builds? BTW, Debian will also sooner or later switch to Python 3 completely so some Python 3 support would be required as well. Kind regards and thanks for providing Core Wrapper as free software Andreas. On Mon, Jul 06, 2015 at 11:05:54AM +0200, Jakub Wilk wrote: The GCC5 build log says: Warning: this seems to be an unsupported operating system. Very suspicious! (I wish upstream build system stopped here, instead of trying to foolishly trying to build stuff anyway...) And in etc/platform.sh there's this: Linux) # Check if it is GCC version 4.x gcc_ver=`gcc --version | grep -e 4\.` if [[ -z $gcc_ver ]] then # It is not GCC version 4.x. Check if it is GCC version 3.x gcc_ver=`gcc --version | grep -e 3\.` if [[ -z $gcc_ver ]] then # It is not GCC version 3.x. Check if it is GCC version 2.x gcc_ver=`gcc --version | grep -e 2\.` if [[ -z $gcc_ver ]] then # It is not GCC version 2.x either. Production can not be compiled. sysid=unknown else # It is GCC version 2.x sysid=gnu2 fi else # It is GCC version 3.x sysid=gnu3 fi else # It is GCC version 4.x sysid=gnu4 fi ;; which doesn't take existence of GCC 5 (or later versions) into account. -- Jakub Wilk ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777971: Help with libtool needed (Was: Bug#777971: librcsb-core-wrapper: ftbfs with GCC-5)
Hi, when trying to hunt down this bug libtool stumbles even at an earlier point - and it remains unclear to me in how libtool is affected by gcc changes. ... Making cctbx make[3]: Entering directory '/tmp/buildd/librcsb-core-wrapper-1.005/cctbx' make[3]: Leaving directory '/tmp/buildd/librcsb-core-wrapper-1.005/cctbx' libtool: link: unable to infer tagged configuration libtool: link: specify a tag with `--tag' Makefile:107: recipe for target 'lib/librcsb-core-wrapper.la' failed make[2]: *** [lib/librcsb-core-wrapper.la] Error 1 make[2]: Leaving directory '/tmp/buildd/librcsb-core-wrapper-1.005' dh_auto_build: make -j1 returned exit code 2 ... Any hint how to fix this? Kind regards Andreas. On Thu, Feb 12, 2015 at 10:33:46AM +, Matthias Klose wrote: Package: src:librcsb-core-wrapper Version: 1.005-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/librcsb-core-wrapper_1.005-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] make[3]: *** Waiting for unfinished jobs Makefile:156: recipe for target 'RcsbPlatform.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [CifString.o] Error 1 Makefile:156: recipe for target 'CifString.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [Serializer.o] Error 1 Makefile:156: recipe for target 'Serializer.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [DataInfo.o] Error 1 Makefile:156: recipe for target 'DataInfo.o' failed make[3]: *** [GenString.o] Error 1 Makefile:156: recipe for target 'GenString.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [Exceptions.o] Error 1 Makefile:156: recipe for target 'Exceptions.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. libtool: compile: Try `libtool --help' for more information. make[3]: *** [BlockIO.o] Error 1 make[3]: *** [mapped_vector.o] Error 1 libtool: compile: Try `libtool --help' for more information. Makefile:156: recipe for target 'BlockIO.o' failed Makefile:156: recipe for target 'mapped_vector.o' failed make[3]: *** [RcsbFile.o] Error 1 Makefile:156: recipe for target 'RcsbFile.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [GenCont.o] Error 1 Makefile:156: recipe for target 'GenCont.o' failed make[3]: Leaving directory '/??PKGBUILDDIR??/common' libtool: link: `lib/*.lo' is not a valid libtool object make[2]: *** [lib/librcsb-core-wrapper.la] Error 1 Makefile:107: recipe for target 'lib/librcsb-core-wrapper.la' failed make[2]: Leaving directory '/??PKGBUILDDIR??' dh_auto_build: make -j10 returned exit code 2 make[1]: *** [override_dh_auto_build-nopy] Error 2 debian/rules:19: recipe for target 'override_dh_auto_build-nopy' failed make[1]: Leaving directory '/??PKGBUILDDIR??' make: *** [build-arch] Error 2 debian/rules:14: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ___ Debian-med-packaging mailing list
Bug#777971: Help with libtool needed (Was: Bug#777971: librcsb-core-wrapper: ftbfs with GCC-5)
The GCC5 build log says: Warning: this seems to be an unsupported operating system. Very suspicious! (I wish upstream build system stopped here, instead of trying to foolishly trying to build stuff anyway...) And in etc/platform.sh there's this: Linux) # Check if it is GCC version 4.x gcc_ver=`gcc --version | grep -e 4\.` if [[ -z $gcc_ver ]] then # It is not GCC version 4.x. Check if it is GCC version 3.x gcc_ver=`gcc --version | grep -e 3\.` if [[ -z $gcc_ver ]] then # It is not GCC version 3.x. Check if it is GCC version 2.x gcc_ver=`gcc --version | grep -e 2\.` if [[ -z $gcc_ver ]] then # It is not GCC version 2.x either. Production can not be compiled. sysid=unknown else # It is GCC version 2.x sysid=gnu2 fi else # It is GCC version 3.x sysid=gnu3 fi else # It is GCC version 4.x sysid=gnu4 fi ;; which doesn't take existence of GCC 5 (or later versions) into account. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
