Your message dated Sun, 14 Jul 2024 18:38:58 +0000
with message-id <[email protected]>
and subject line Bug#1075440: fixed in recode 3.6-27
has caused the Debian Bug report #1075440,
regarding recode: ftbfs with GCC-14
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 [email protected]
immediately.)
--
1075440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075440
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:recode
Version: 3.6-26
Severity: important
Tags: sid trixie
User: [email protected]
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
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-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/recode_3.6-26_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are 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-14/porting_to.html
[...]
rm -f stamp-pot
rm -rf doc/recode
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
touch aclocal.m4
touch configure
touch stamp-h.in
touch config.h.in
touch Makefile.in
touch m4/Makefile.in
touch doc/Makefile.in
touch lib/Makefile.in
touch libiconv/Makefile.in
touch i18n/Makefile.in
touch src/Makefile.in
touch tests/Makefile.in
touch contrib/Makefile.in
dh_auto_configure -- --without-included-gettext
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --without-included-gettext
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking how to suppress newlines using echo... escape
checking for gcc... gcc
checking whether the C compiler (gcc -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wl,-z,relro) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:741: checking for a BSD compatible install
configure:794: checking whether build environment is sane
configure:851: checking whether make sets ${MAKE}
configure:897: checking for working aclocal-1.4
configure:910: checking for working autoconf
configure:923: checking for working automake-1.4
configure:936: checking for working autoheader
configure:949: checking for working makeinfo
configure:965: checking how to suppress newlines using echo
configure:996: checking for gcc
configure:1109: checking whether the C compiler (gcc -g -O2
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wl,-z,relro) works
configure:1125: gcc -o conftest -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
-Wl,-z,relro conftest.c 1>&5
configure:1122:1: error: return type defaults to 'int' [-Wimplicit-int]
1122 | main(){return(0);}
| ^~~~
configure: failed program was:
#line 1120 "configure"
#include "confdefs.h"
main(){return(0);}
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --without-included-gettext returned exit code 1
make[1]: *** [debian/rules:34: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: recode
Source-Version: 3.6-27
Done: Santiago Vila <[email protected]>
We believe that the bug you reported is fixed in the latest version of
recode, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila <[email protected]> (supplier of updated recode 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 14 Jul 2024 19:10:00 +0200
Source: recode
Architecture: source
Version: 3.6-27
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <[email protected]>
Changed-By: Santiago Vila <[email protected]>
Closes: 1047159 1075440
Changes:
recode (3.6-27) unstable; urgency=medium
.
* Fix FTBFS with gcc-14. Closes: #1075440.
* Setting DEB_CFLAGS_MAINT_STRIP is no longer needed.
* Raise debhelper compat level to 13. We can finally do this
because the configure script has been updated.
* Remove more files in dh_auto_clean. Closes: #1047159.
Checksums-Sha1:
d38095c284f6e6cf1556f1b604a4972a50d598e4 1489 recode_3.6-27.dsc
841747ff6fc286e4edb4e4359b71e2edcf693630 221780 recode_3.6-27.debian.tar.xz
41b413e3d499802f0ca06498fce1dad8d15418ff 5475 recode_3.6-27_source.buildinfo
Checksums-Sha256:
0de83169db71ece79c4514d0f2a6324a118c4e931faf301cb85f1d3b8ba4593a 1489
recode_3.6-27.dsc
99b0621f60869aea0046d0c0b760e2135c6ffece18baf43e6513f44582a6e774 221780
recode_3.6-27.debian.tar.xz
89aa779c6d1cf093548a9842f1df3dcd32d7853abb1220cfbeda852fbe6ae41a 5475
recode_3.6-27_source.buildinfo
Files:
0829c19d3463502a08d69fbdab91bb6f 1489 text optional recode_3.6-27.dsc
b575e32e59eaaca095aefe557830d16b 221780 text optional
recode_3.6-27.debian.tar.xz
57eca086dd26ed9437f7540d14c534fc 5475 text optional
recode_3.6-27_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmaUFG8ACgkQQc5/C58b
izK9JAf/W+XqxMbiBXrTZbm63IB65TE188eGPK6pWmpdZBzXkKN/fVguuHv9+njy
z7i9FEbvqbuXej8gUtp6yGc1EukEwn1Xvr4Q19yQU9HfC0bxPKxUxXJGedVluIC5
ymhV7GupY8q13U+/9LKywXTZXbOPpVxhBol8RfxjWvWoT9l4UIPm8Y+iRKQ6xLX2
2Rza7udGYQpBwDHcAyzSeAhu48YQl1ZB6oBn+4ExhdpuOUeJxAsXlz1yIjfaTbrB
NbfOp9+Uq5Nuu7DolR3TsOHexWM3b0yv9230cLjufzKPpirXQLYWIUerhAcOCQEG
tUi/U8WIh72TLSv2sKzp9wMn9YXNvg==
=YZrM
-----END PGP SIGNATURE-----
pgpo8yyEXacO7.pgp
Description: PGP signature
--- End Message ---
