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

Bug#1074919: marked as done (dot-forward: ftbfs with GCC-14)

Your message dated Wed, 21 Aug 2024 06:22:53 +0000
with message-id <E1sgek9-00ANPy-2W@fasolo.debian.org>
and subject line Bug#1074919: fixed in dot-forward 1:0.71-8
has caused the Debian Bug report #1074919,
regarding dot-forward: 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 owner@bugs.debian.org
immediately.)


-- 
1074919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074919
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:dot-forward
Version: 1:0.71-7
Severity: important
Tags: sid trixie
User: debian-gcc@lists.debian.org
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/dot-forward_0.71-7_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

[...]
   dh_auto_build
	make -j8 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<<PKGBUILDDIR>>'
( cat warn-auto.sh; \
echo CC=\'`head -1 conf-cc`\'; \
echo LD=\'`head -1 conf-ld`\' \
) > auto-ccld.sh
nroff -man dot-forward.1 > dot-forward.0
cat auto-ccld.sh make-load.sh > make-load
cat auto-ccld.sh find-systype.sh > find-systype
cat auto-ccld.sh make-compile.sh > make-compile
cat auto-ccld.sh make-makelib.sh > make-makelib
chmod 755 make-load
chmod 755 find-systype
chmod 755 make-compile
chmod 755 make-makelib
./find-systype > systype
( cat warn-auto.sh; ./make-load "`cat systype`" ) > load
( cat warn-auto.sh; ./make-compile "`cat systype`" ) > \
compile
( cat warn-auto.sh; ./make-makelib "`cat systype`" ) > \
makelib
chmod 755 makelib
chmod 755 load
chmod 755 compile
./compile dot-forward.c
./compile control.c
./compile auto-str.c
./compile substdio.c
./compile substdi.c
./compile substdo.c
./compile subfderr.c
./compile substdio_copy.c
In file included from auto-str.c:1:
substdio.h:12:64: error: initialization of ‘int (*)()’ from incompatible pointer type ‘ssize_t (*)(int,  const void *, size_t)’ {aka ‘long int (*)(int,  const void *, long unsigned int)’} [-Wincompatible-pointer-types]
   12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
      |                                                                ^
auto-str.c:6:16: note: in expansion of macro ‘SUBSTDIO_FDBUF’
    6 | substdio ss1 = SUBSTDIO_FDBUF(write,1,buf1,sizeof(buf1));
      |                ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘ss1.op’)
   12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
      |                                                                ^
auto-str.c:6:16: note: in expansion of macro ‘SUBSTDIO_FDBUF’
    6 | substdio ss1 = SUBSTDIO_FDBUF(write,1,buf1,sizeof(buf1));
      |                ^~~~~~~~~~~~~~
In file included from subfderr.c:2:
substdio.h:12:64: error: initialization of ‘int (*)()’ from incompatible pointer type ‘ssize_t (*)(int,  const void *, size_t)’ {aka ‘long int (*)(int,  const void *, long unsigned int)’} [-Wincompatible-pointer-types]
   12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
      |                                                                ^
subfderr.c:6:22: note: in expansion of macro ‘SUBSTDIO_FDBUF’
    6 | static substdio it = SUBSTDIO_FDBUF(write,2,subfd_errbuf,256);
      |                      ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘it.op’)
   12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
      |                                                                ^
subfderr.c:6:22: note: in expansion of macro ‘SUBSTDIO_FDBUF’
    6 | static substdio it = SUBSTDIO_FDBUF(write,2,subfd_errbuf,256);
      |                      ^~~~~~~~~~~~~~
make[1]: *** [Makefile:32: auto-str.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:358: subfderr.o] Error 1
dot-forward.c: In function ‘blindwrite’:
dot-forward.c:64:3: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
   64 |   write(fd,buf,len);
      |   ^~~~~~~~~~~~~~~~~
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: dot-forward
Source-Version: 1:0.71-8
Done: Andreas Beckmann <anbe@debian.org>

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

Debian distribution maintenance software
pp.
Andreas Beckmann <anbe@debian.org> (supplier of updated dot-forward 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Wed, 21 Aug 2024 07:42:56 +0200
Source: dot-forward
Architecture: source
Version: 1:0.71-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Beckmann <anbe@debian.org>
Closes: 1074919
Changes:
 dot-forward (1:0.71-8) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with GCC 14.  (Closes: #1074919)
   * Make the build process verbose.
Checksums-Sha1:
 52b98fa6601b87b883afb8c2a12795b93ceebcbe 1897 dot-forward_0.71-8.dsc
 031db9959289efc4d1f7c20d68b9964f23e65b6e 5708 dot-forward_0.71-8.debian.tar.xz
 ce55630ccadabf5ae100418d352906ba73283921 5372 dot-forward_0.71-8_source.buildinfo
Checksums-Sha256:
 69125c0ecdbdfe41887c6dea69db15bbddd11139060b1cecb790ab178c3f5213 1897 dot-forward_0.71-8.dsc
 1b114ad9d7b8b2208865967d9ca448a71828b8ca3c434368a3d8fb4ffc955472 5708 dot-forward_0.71-8.debian.tar.xz
 d7bfe4d7b020eef9ab533245f2a677e0762ac82d267d3839cf5623626b19bf31 5372 dot-forward_0.71-8_source.buildinfo
Files:
 c4d84ff7a5c93ba2bebd8eae5be0b922 1897 mail optional dot-forward_0.71-8.dsc
 510c822f583ccc64979637db3a8c5e55 5708 mail optional dot-forward_0.71-8.debian.tar.xz
 e3412f34cc9c114ceeacdb2b1192f608 5372 mail optional dot-forward_0.71-8_source.buildinfo

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

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmbFf9MQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKqjD/9dTGPsWJA0mX7PoAKC5zxLmATzO1xUt8Pb
v+pgDiOyWgpU+mWJyqMTEEDX1DUu85DLE6UEXwedFKLCjXyBQdioihia5Bg6g5GP
2yHYidj8lAOkK2mn1y14q1jJYiZcnksIgmiI9lkL1HyAQmZZZMmJrIf0jFrwf5yh
hWxJX9YPPeBmJNr5+etnWqHIRrHB5BdI8jdD3gJDItdntPvdA4rLDHlP6KXSs7VY
hu0IDu535c0iMrG92feODHoqY9rqTwckk8jjWPBgnnC5rEsyBOepYPdkMTVplvzi
N6fytSE8RXAUN5WB9svGuLqGpnc8EWqZoPi0hZbThJcTqzRBZB+Zy0Y6CfFcZPp/
8K1LRNg/9z/GeYe40lQLX9Bq6DhIoShfAhaRAW0XpKqMHOASg+TMabl2nV/rLDMq
96q1Q8pWt0b3FK2eKv/025ScfMA4DZVF07IrADt3X4y/i399nr02zZf4tJL7BW38
F2L/lpGxHXrkuitw2eG8LIu8TkPY3Ymo9gvm24ZAKpbQCoQBEdcBQ0QAwX18S0Q9
KHy6JHJQZo4ZPQrOk7qgyCV4yPn1IDNXPcXUaOV0KKCspI4wffenfPn0abLWgnbR
1ap0C/sM9eXcydZ+QYWv+7gm8Midrma7xkXwV4WivNRRJeOcy9yq3jTTXi6gqyAb
BsiRhxq/RQ==
=g3//
-----END PGP SIGNATURE-----

Attachment: pgpYfewXKDjYH.pgp
Description: PGP signature


--- End Message ---
Reply to: