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

Bug#1096838: marked as done (ink: ftbfs with GCC-15)



Your message dated Tue, 09 Sep 2025 03:27:38 +0000
with message-id <E1uvp18-00GruS-1I@fasolo.debian.org>
and subject line Bug#1096838: fixed in ink 0.5.3-7
has caused the Debian Bug report #1096838,
regarding ink: ftbfs with GCC-15
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.)


-- 
1096838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096838
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:ink
Version: 0.5.3-6
Severity: important
Tags: sid forky
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT 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-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/ink_0.5.3-6_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other 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-15/porting_to.html

[...]
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking how to run the C preprocessor... gcc -E
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking for rpmbuild... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for inklevel.h... yes
checking for get_ink_level in -linklevel... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating ink.spec
config.status: creating ink.1
config.status: creating config.h
config.status: executing depfiles commands
   dh_auto_build
	make -j8
make[1]: Entering directory '/build/reproducible-path/ink-0.5.3'
make  all-am
make[2]: Entering directory '/build/reproducible-path/ink-0.5.3'
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ink-0.5.3=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIE -c -o ink.o ink.c
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ink-0.5.3=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIE -c -o malloc.o malloc.c
malloc.c:6:7: warning: conflicting types for built-in function ‘malloc’; expected ‘void *(long unsigned int)’ [-Wbuiltin-declaration-mismatch]
    6 | void *malloc ();
      |       ^~~~~~
malloc.c:5:1: note: ‘malloc’ is declared in header ‘<stdlib.h>’
    4 | #include <sys/types.h>
  +++ |+#include <stdlib.h>
    5 | 
malloc.c: In function ‘rpl_malloc’:
malloc.c:16:10: error: too many arguments to function ‘malloc’; expected 0, have 1
   16 |   return malloc (n);
      |          ^~~~~~  ~
malloc.c:6:7: note: declared here
    6 | void *malloc ();
      |       ^~~~~~
make[2]: *** [Makefile:450: malloc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/build/reproducible-path/ink-0.5.3'
make[1]: *** [Makefile:327: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/ink-0.5.3'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: ink
Source-Version: 0.5.3-7
Done: Thorsten Alteholz <debian@alteholz.de>

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

Debian distribution maintenance software
pp.
Thorsten Alteholz <debian@alteholz.de> (supplier of updated ink 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: SHA512

Format: 1.8
Date: Mon, 08 Sep 2025 22:33:20 +0200
Source: ink
Architecture: source
Version: 0.5.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Changed-By: Thorsten Alteholz <debian@alteholz.de>
Closes: 1096838
Changes:
 ink (0.5.3-7) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.7.2 (no changes)
   * add gcc15.patch (Closes: #1096838)
Checksums-Sha1:
 7234f13b16d75081e2906be0c25643d27ae9d2d9 2032 ink_0.5.3-7.dsc
 90177a5272717017968eb09c4180652b18a62ea3 111791 ink_0.5.3.orig.tar.gz
 69bcb8ea88d321287d716b77da3e1188f3b04644 4060 ink_0.5.3-7.debian.tar.xz
 0d2487846b3b11bf5c97a078091f6802c01ca645 6216 ink_0.5.3-7_amd64.buildinfo
Checksums-Sha256:
 ab0a373abba9f348275b697ba43d3e34540c2e3738d8cd6447555926eb6f7247 2032 ink_0.5.3-7.dsc
 2d318fb6a826ef3a2c7cd1e889f42971fd7ae682e3e0ba471c8a0016375a60ba 111791 ink_0.5.3.orig.tar.gz
 abdbbf7e66220972bb5c29e580f377b4f5be21c2f1aea3d17ced00fa66e933a1 4060 ink_0.5.3-7.debian.tar.xz
 f52d2c88d0a658429125473a9fd092211858a9bb0d0e817557fbace8198095d3 6216 ink_0.5.3-7_amd64.buildinfo
Files:
 b3c073b0b0b09eb55e5af8828ecc0f63 2032 admin optional ink_0.5.3-7.dsc
 7ddb245c1b0314a4348f2a43e8d37885 111791 admin optional ink_0.5.3.orig.tar.gz
 9ff81fcb5d6fcef8b04cfb00805cee61 4060 admin optional ink_0.5.3-7.debian.tar.xz
 f56d6a18b0e5d38048bfa32cf5f13622 6216 admin optional ink_0.5.3-7_amd64.buildinfo

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

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmi/UHpfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR/p6D/sFgUMxBa8mNSYafhfFNg3D/9OGLHOh
Lufmh0D8Aca8qVcQ8/I9dAdQeRm86eI/Uigzkw+c0K6ZLXXu3AI2kPVv9It/EXbs
XY+0cknXMj1moGJ/gAI1MnCo6DBdomARu35gj/iT90F0WP3lKF/0oCx8Ou97nFbV
0WEXwzvOCp8IVKMozssLgU4V0v8gAJyRlpyUEiY4ixSB1aVUJNsFsfkn1ML3yn0f
N+gPmiUwwdGRBv+pAij7Nitd1A0Svm+dPYSosSPB927qJqmowbub6T2TUxKGY/Zg
dNSIxn1xp2YBPTA1ydYfhTEOAtV2tPuMl2v2YBPWqs8OCVJHKu4XsLTRLQZLdxtY
ABs/+fIffmxq8WZt0mUSazYe8Wkeu3IjVKN38JYjCQB/gtXL1zGEiQRWpYJwbFO8
Sdxk4Pg2KmlItc7gs5uCsKNCiJOyM8ng0aBJsif1Zy1xAwtnvLQOXWm9tP5+CMJ+
IqSRAZAphLoDpchktg9FwcI4FFhUf4TKuNtVr4rg4Y4MhVeRvYLsNr5lKjJStGwc
2lkltio7KDIGrG09dwLvO1tr3r/6EV60lBPl9iw0WY4sLaCKGnG/I3447oa79GyL
IUhFFbpBvtjCJO0Wv2N7fBINsYbDVw/y6utHDJlt9r5UQ2VYT4MNsUfRLhIFts3R
MMBT7P1IUfk+4Q==
=ZzMQ
-----END PGP SIGNATURE-----

Attachment: pgpx_OfpIwwU6.pgp
Description: PGP signature


--- End Message ---

Reply to: