Your message dated Sun, 20 Mar 2016 16:38:04 +0000
with message-id <e1ahgme-0008tc...@franck.debian.org>
and subject line Bug#818715: fixed in ros-image-common 1.11.10-5
has caused the Debian Bug report #818715,
regarding ros-image-common: FTBFS on several architectures: relocation 
R_X86_64_PC32 against symbol `_ZTVN7testing8internal17TestEventRepeaterE' can 
not be used when making a shared object; recompile with -fPIC
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.)


-- 
818715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-image-common
Version: 1.11.10-4
Severity: serious

Your package failed to build on several architectures:

/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: relocation R_X86_64_PC32 
against symbol `_ZTVN7testing8internal17TestEventRepeaterE' can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

It looks as if that file was compiled with -fPIC though:

cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/gtest && /usr/bin/c++   
-DGTEST_CREATE_SHARED_LIBRARY=1 -Dgtest_EXPORTS -I/usr/src/gtest/include 
-I/usr/src/gtest  -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wall -Wshadow -DGTEST_HAS_PTHREAD=1 -fexceptions -Wextra 
-Wno-unused-parameter -Wno-missing-field-initializers -o 
CMakeFiles/gtest.dir/src/gtest-all.cc.o -c /usr/src/gtest/src/gtest-all.cc

On ppc64el the error is a bit different, but it also points to -fPIC so the
problem is likely the same:

/usr/bin/c++  -fPIC -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,libgtest.so -o libgtest.so 
CMakeFiles/gtest.dir/src/gtest-all.cc.o  
-L/«PKGBUILDDIR»/obj-powerpc64le-linux-gnu/gtest/src -lpthread 
-Wl,-rpath,/«PKGBUILDDIR»/obj-powerpc64le-linux-gnu/gtest/src 
/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: In function 
`testing::internal::FormatCxxExceptionMessage(char const*, char const*)':
/usr/src/gtest/src/gtest.cc:2030:(.text.unlikely+0x80): call to 
`testing::Message::Message()' lacks nop, can't restore toc; recompile with -fPIC
/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: In function 
`testing::Message::GetString[abi:cxx11]() const':
/usr/src/gtest/src/gtest.cc:947:(.text.unlikely+0x150): call to 
`testing::internal::StringStreamToString(std::__cxx11::basic_stringstream<char, 
std::char_traits<char>, std::allocator<char> >*)' lacks nop, can't restore toc; 
recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

Full logs at:
https://buildd.debian.org/status/logs.php?pkg=ros-image-common&ver=1.11.10-4

Cheers,
Emilio

--- End Message ---
--- Begin Message ---
Source: ros-image-common
Source-Version: 1.11.10-5

We believe that the bug you reported is fixed in the latest version of
ros-image-common, which is due to be installed in the Debian FTP archive.

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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo <mat...@debian.org> (supplier of updated ros-image-common 
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...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 20 Mar 2016 16:16:08 +0000
Source: ros-image-common
Binary: libcamera-calibration-parsers-dev libcamera-calibration-parsers0d 
camera-calibration-parsers-tools python-camera-calibration-parsers 
libcamera-info-manager-dev libcamera-info-manager0d libimage-transport-dev 
libimage-transport0d image-transport-tools libpolled-camera-dev 
libpolled-camera0d polled-camera-tool python-polled-camera cl-polled-camera
Architecture: source
Version: 1.11.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Mattia Rizzolo <mat...@debian.org>
Description:
 camera-calibration-parsers-tools - Robot OS camera_calibration_parsers_tools 
package
 cl-polled-camera - Robot OS polled_camera package - LISP
 image-transport-tools - Robot OS image_transport package tools
 libcamera-calibration-parsers-dev - Robot OS camera_calibration_parsers 
package - development
 libcamera-calibration-parsers0d - Robot OS camera_calibration_parsers package
 libcamera-info-manager-dev - Robot OS camera_info_manager package - development
 libcamera-info-manager0d - Robot OS camera_info_manager package
 libimage-transport-dev - Robot OS image_transport package - development
 libimage-transport0d - Robot OS image_transport package
 libpolled-camera-dev - Robot OS polled_camera package - development
 libpolled-camera0d - Robot OS polled_camera package
 polled-camera-tool - Robot OS polled_camera package tool
 python-camera-calibration-parsers - Robot OS camera_calibration_parsers Python 
package
 python-polled-camera - Robot OS polled_camera package - Python
Closes: 818715
Changes:
 ros-image-common (1.11.10-5) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules: disable -pie from the hardening buildflags.
     Fix FTBFS in several architectures.  Closes: #818715
     This was caused by a latent bug triggerend by my cleanup in the last 
upload.
Checksums-Sha1:
 07cd25b47c80581e08c53e0aeba6957885acdb90 3495 ros-image-common_1.11.10-5.dsc
 56b7e6a96dc7f1d0dd8d99efe90b3b30df7ccca3 5404 
ros-image-common_1.11.10-5.debian.tar.xz
Checksums-Sha256:
 d62ea03698e2612baa0b1c5f2310714cd553016952c964a52f8a767afa038d31 3495 
ros-image-common_1.11.10-5.dsc
 4288cba2f3fb1e53f1f6c12013e7a909d43db2857b4880a5d980fe3afd7b6938 5404 
ros-image-common_1.11.10-5.debian.tar.xz
Files:
 ebef39e4762b6cc38cbd0d2936a89b06 3495 libs optional 
ros-image-common_1.11.10-5.dsc
 f8c39b43962efe84ed69b51772e73a66 5404 libs optional 
ros-image-common_1.11.10-5.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJW7s4lAAoJEEsEP825REVAx4cP/jiRmBtykW4wqW1AepX2fYZA
KQMn4NzU6k9BCwFVXfRSNIp49X8xXw32ameOFOhixpwBjmBuOTvYaXkzwYAxRfTf
JiZd41gyZvAjyyIrcwGPNoy7TunxkfqJ3ojkcING6YBoqomxnHdZLkEHO7cSOlBI
bMyj/8w/wbY7Nztw8OVQR72dpiBGglGrrwPhw+6JpUXb2DkPdHIulTpjmDdXpBgO
5b2cQKJunhsmcHG6jtmt5s6O7AryDFl2u1Q0I9mRvMpcUzIXyBObKGmpYmbtiRp2
DBnMrl9bbUrXNCV3KiO1pSHaLsyxDcPhEFgUJZSGl57BQ+pVs1VD+7iOSu5+ACaM
mu3eBYWWapD51nR9JLjf+xs3RRACGBOh/hI4+i7W42ZGZ4dEXA70fgobpRbRUFSH
kwEDdO7R6h62r9EN+0vsYHwSYk1Btiw7KQv36qCorToDZm0zF0lFQFZ6B93FrehT
K4V17TesEi6Xy5O56lZ91yUExDhl+DLuuxlyPGh4DbAg2FJgGs5t7srPMp+nmPfg
zcfMyFtxFtB0+rAQUjZk8Fpx0sXLyq3eTcjNW7LVhCppkpC8VZci9O0HGbbGGBNu
UET5MBE3SHojFQZeaKl4g9ZPJrSCqhvWGo2VgOOU9JOeIFZ0jSewWKxKoYkIAitx
Tc/j8SsYc+UuIlXmbjdn
=i0PK
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to