[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#841940: marked as done (nmu: antlr_2.7.7+dfsg-7)

Your message dated Tue, 25 Oct 2016 05:30:00 +0000
with message-id <03980ccd-5e66-a7cb-3b9c-2e6029348712@thykier.net>
and subject line Re: nmu: antlr_2.7.7+dfsg-7
has caused the Debian Bug report #841940,
regarding nmu: antlr_2.7.7+dfsg-7
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 owner@bugs.debian.org
immediately.)


-- 
841940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841940
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

The antlr package currently in unstable isn't built with -fPIC, leading to FTFS for some of its reverse dependencies, such as nco:
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/ncap2 Invoke.o ncap2.o ncap2_utl.o sdo_utl.o sym_cls.o fmc_cls.o fmc_all_cls.o fmc_gsl_cls.o prs_cls.o NcapVar.o NcapVarVector.o ncoLexer.o ncoParser.o ncoTree.o nco_gsl.o  -L../nco /<<PKGBUILDDIR>>/src/nco/.libs/libnco.so -lantlr -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu/hdf5/serial -lhdf5_hl -lhdf5 -lpthread -lsz -lz -ldl -lnetcdf /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so -lgsl -lgslcblas -lm -ludunits2 -pthread -fopenmp -Wl,-rpath -Wl,/usr/lib/nco
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libantlr.a(ASTFactory.o): relocation R_X86_64_32S against symbol `_ZTVN5antlr10ASTFactoryE' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libantlr.a(BaseAST.o): relocation R_X86_64_32S against symbol `_ZNK5antlr7BaseAST13getFirstChildEv' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libantlr.a(BitSet.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
...

Binnmu-ing seems sufficient to fix that (tested localy on my box).

nmu antlr_2.7.7+dfsg-7 . ANY . unstable . -m "rebuild with -fPIC"

Thanks in advance,

_g.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYDj76AAoJEO/obGx//s+Dar0IAJbQSE3DicxF9tGYOx8xgQKU
ZPqfLcdDMhHOZS6Q+MXrc1Ft3Ol24QuHKFrZNPGBI8sbNgQR1i32YykgaU9IkrOj
esmviFXXhEy+WnjcKyGEG8AL0CIc/atsTjV0U4M7aehTapkDVucRwzfHYEXcCCeY
sC5Xdhe60/iyOhL8TbmeeT1dExM7zAUNv7HJ6D4zFZq/fJxsqKoYdrkleG/PJ/5e
8JnF3UrhTH9au1MIZUHXZ5inCD5n5Kcb2nIprSfK1+TtfDTMRNxrnInYQvN7N0QL
XG1w0TftNCmIsVtxyaVdEyKmkwR4Oo+ko+81BzZt465h4OHHK1a2uU9Y/IRP9os=
=JPC4
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On Mon, 24 Oct 2016 19:04:03 +0200 Gilles Filippini <pini@debian.org> wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> Hi,
> 
> The antlr package currently in unstable isn't built with -fPIC, leading to FTFS for some of its reverse dependencies, such as nco:
> [...]
> 
> Binnmu-ing seems sufficient to fix that (tested localy on my box).
> 
> nmu antlr_2.7.7+dfsg-7 . ANY . unstable . -m "rebuild with -fPIC"
> 
> Thanks in advance,
> 
> _g.
> 
> [...]

Scheduled, thanks.

~Niels

--- End Message ---
Reply to: