Your message dated Sun, 28 Aug 2016 23:50:43 +0000
with message-id <e1be9qd-0002uj...@franck.debian.org>
and subject line Bug#835540: fixed in log4cpp 1.1.1-2
has caused the Debian Bug report #835540,
regarding Missing dependencies at linktime
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.)


-- 
835540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: log4cpp
Version: Missing Dependencies
Severity: serious

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

Hello,

at link time log4cpp produce this errors:


libtool: link: g++ -g -O2 -fdebug-prefix-map=/build/bitz-server-1.0.0=. -fPIE
- -fstack-protector-strong -Wformat -Werror=format-security -fPIE -pie -Wl,-z
- -Wl,relro -Wl,-z -Wl,now -o .libs/bitz-server main.o bitz-server.o
bitz/exception.o bitz/manager_exception.o bitz/config.o bitz/logger.o
bitz/util.o bitz/manager.o bitz/worker.o bitz/request_handler.o
bitz/options_request_handler.o bitz/reqmod_request_handler.o
bitz/respmod_request_handler.o bitz/modifier.o -Wl,--export-dynamic  -ldl
../lib/icap/.libs/libicap.so -lconfig++ -llog4cpp -lnsl /usr/lib/x86_64-linux-
gnu/libpsocksxx.so
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_getspecific'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_key_delete'
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/liblog4cpp.so:
undefined reference to `pthread_setspecific'
collect2: error: ld returned 1 exit status


This looks like missing dependencies from log4cpp.

CU
Jörg



- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

iQIcBAEBCgAGBQJXwJeyAAoJEAn4nzyModJdz2gQAIyx2uSvUofq66c5YT49UDv7
O0UX0D5eSA+DfiDYq6PDwBM1F7lsRaiwoQdFosN1K+nNS5Hf3ujz4gaSx9q1bXcy
zmuD3ZvZxA0IL1b1736bKtFGeEyOxldkm22F3aqt9u3w/NIMPFm4zzfO4KgstREE
r0w3EjpD+Ao+I0j0lR/8uSQ7vOhxEuA8so8dBitjulBwPbYnuGL+T8sudX0SUI/C
T5Fl2BFkNnIHwPn5wG1i/9WRG1ObqDQq9MFJ4DmraUc5JfLKmGwNeQg9ZZMEeSWh
52Omv/k8Phq1Mxdhab9bSDK1Jmuj4JtJyD2Z3woRkjqjr//X6biyzSIDRzm5Mfg4
LtxFzFK1zLqZxtQBuWt7NxtYuhZxv3recOSZbepDW7y+10IICvoPUWfeFTs4+OSu
f3QzD0S1uAgLVumGjYAIOJ2x72GlopuYaoM2NjTDxntaQu7YpcZdKXoHMEdbHxYy
Nq8FSAfgiGp1ng+OQw7J2tyAKNVwWpjyC4twWql3TBgbMhrLe1ZtIiNHkDyLK/RI
diCmP2Yz0ZPX2EU5dP5M9TxNfem+tQrqUtOViteEajy5vj5i8/J62zAV72+LSI5Y
PyqgotgwkxRw0hN2b9WreHYu6rUmDMt9O9XjVSwPc1JUwJh+bzPbIqoEb+/xxcmm
HnpgZElB/ZHvwPJwlvdm
=YS19
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: log4cpp
Source-Version: 1.1.1-2

We believe that the bug you reported is fixed in the latest version of
log4cpp, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms <bott...@debian.org> (supplier of updated log4cpp 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: SHA256

Format: 1.8
Date: Sun, 28 Aug 2016 18:00:54 -0400
Source: log4cpp
Binary: liblog4cpp5-dev liblog4cpp5v5
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Fathi Boudra <f...@debian.org>
Changed-By: A. Maitland Bottoms <bott...@debian.org>
Description:
 liblog4cpp5-dev - C++ library for flexible logging (development)
 liblog4cpp5v5 - C++ library for flexible logging (runtime)
Closes: 835540 835795 835819
Changes:
 log4cpp (1.1.1-2) unstable; urgency=medium
 .
   * fix pthreads configuration (Closes: #835540, #835819)
   * fix Vcs-Git URL (Closes: #835795)
Checksums-Sha1:
 da156a724e57d526385ccfa78d2d601c2f06f3bb 1978 log4cpp_1.1.1-2.dsc
 1e943c63e9e3b0596a60b16c9553e582dd48b059 95356 log4cpp_1.1.1-2.debian.tar.xz
Checksums-Sha256:
 2967de5566065b79c5179c5084f0a35e4d5eda47077a348feeb1028e42199dd0 1978 
log4cpp_1.1.1-2.dsc
 ffbd7ffe63ef46cee89b9a39687a60b914057c0647aaa1e9bed98f505e83f4ff 95356 
log4cpp_1.1.1-2.debian.tar.xz
Files:
 e9c757fb884e17f7bf7977ad50ad8249 1978 libs optional log4cpp_1.1.1-2.dsc
 9c85a831da6e624a86ea2a7d07b6fda6 95356 libs optional 
log4cpp_1.1.1-2.debian.tar.xz

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

iQIcBAEBCAAGBQJXw3jRAAoJEFBB8YkfROCQJDoP/3wtd04jdb1/hCDMNWKgUbbC
T/b1PpUQqqE6hHXbvApmzoxZ/t5dCpDmvLi78gYzkIwOiTRcav+DflX9mQP/Ic1N
B6cvbjK+wN9x6nwfqCPMsCZ8QR/BJXuP5NkD/aCuNjNTBshLRgyRTylfxpppvauo
6jXx8jMp3ppriscsMZdLFc+60FDL91zCfik11077zBQvtwFHaH2GmI3LTDbY6InF
VsQ202SFjt1OKMiXY6vTA5ySpKGe6UklMTryxLSTRdkPBPyR76lyQJQSFAnagPnp
SdknAXTM8PJ2lfvdPJesTRRpSScnT9JI1LKC9hTsd1PIAjYtqjpr19gcaT65wtQM
cWDmtYY9tLbnTBWZuEOYyynVVnnXfRD2fhUXfGRqwyhAC+bMV3mK7V5uL7WSbL/X
r438KmgT4bBoY3Dk1IAakzr7vBywb/YNfuMlwjNPiPeWRR2T48edio46tuYzXWLy
R1yN0d1Lg+9GcMMB4azI588X5TMziZ+UdmiVAY7/cdVrLQwt+He3SmEAQ9FBeSS7
O1SvjELhNaNeNQNP7qUYuqkMVSzVoUVqlma9leN0LtC+3SDj1YgQITMBURt08Ptn
+KCdDf33JAT46+P+uIt3Df3BIii/FKyIhZnhu504jiV277VCKIbb4Fikm37u9jr+
NnRbLPp+Ul3YjWYVuQ+0
=CMEA
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to