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

Bug#1097795: marked as done (rlpr: ftbfs with GCC-15)

Your message dated Mon, 15 Sep 2025 22:05:23 +0000
with message-id <E1uyHK7-00E4lr-1h@fasolo.debian.org>
and subject line Bug#1097795: fixed in rlpr 2.06-3
has caused the Debian Bug report #1097795,
regarding rlpr: 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.)


-- 
1097795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097795
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:rlpr
Version: 2.06-2
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/rlpr_2.06-2_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

[...]
error.c:46:6: warning: conflicting types for built-in function ‘exit’; expected ‘void(int)’ [-Wbuiltin-declaration-mismatch]
   46 | void exit ();
      |      ^~~~
error.c:30:1: note: ‘exit’ is declared in header ‘<stdlib.h>’
   29 | #  include <stdarg.h>
  +++ |+#include <stdlib.h>
   30 | #  define VA_START(args, lastarg) va_start(args, lastarg)
error.c:82:7: error: conflicting types for ‘strerror’; have ‘char *(void)’
   82 | char *strerror ();
      |       ^~~~~~~~
In file included from error.c:25:
/usr/include/string.h:419:14: note: previous declaration of ‘strerror’ with type ‘char *(int)’
  419 | extern char *strerror (int __errnum) __THROW;
      |              ^~~~~~~~
error.c: In function ‘error’:
error.c:143:30: error: too many arguments to function ‘strerror’; expected 0, have 1
  143 |     fprintf (stderr, ": %s", strerror (errnum));
      |                              ^~~~~~~~  ~~~~~~
error.c:82:7: note: declared here
   82 | char *strerror ();
      |       ^~~~~~~~
error.c:147:5: error: too many arguments to function ‘exit’; expected 0, have 1
  147 |     exit (status);
      |     ^~~~  ~~~~~~
error.c:46:6: note: declared here
   46 | void exit ();
      |      ^~~~
error.c: In function ‘error_at_line’:
error.c:211:30: error: too many arguments to function ‘strerror’; expected 0, have 1
  211 |     fprintf (stderr, ": %s", strerror (errnum));
      |                              ^~~~~~~~  ~~~~~~
error.c:82:7: note: declared here
   82 | char *strerror ();
      |       ^~~~~~~~
error.c:215:5: error: too many arguments to function ‘exit’; expected 0, have 1
  215 |     exit (status);
      |     ^~~~  ~~~~~~
error.c:46:6: note: declared here
   46 | void exit ();
      |      ^~~~
In file included from xstrtol.c:57:
xstrtol.c: In function ‘xstrtol’:
xstrtol.h:10:21: warning: old-style function definition [-Wold-style-definition]
   10 | #  define __xstrtol xstrtol
      |                     ^~~~~~~
xstrtol.c:73:1: note: in expansion of macro ‘__xstrtol’
   73 | __xstrtol (s, ptr, base, val, valid_suffixes)
      | ^~~~~~~~~
xstrtol.h:11:20: error: too many arguments to function ‘strtol’; expected 0, have 3
   11 | #  define __strtol strtol
      |                    ^~~~~~
xstrtol.c:89:9: note: in expansion of macro ‘__strtol’
   89 |   tmp = __strtol (s, p, base);
      |         ^~~~~~~~
xstrtol.h:11:20: note: declared here
   11 | #  define __strtol strtol
      |                    ^~~~~~
xstrtol.c:68:21: note: in expansion of macro ‘__strtol’
   68 | __unsigned long int __strtol ();
      |                     ^~~~~~~~
make[3]: *** [Makefile:221: error.o] Error 1
make[3]: *** [Makefile:221: xstrtol.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/rlpr-2.06/lib'
make[2]: *** [Makefile:189: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/rlpr-2.06'
make[1]: *** [Makefile:142: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/rlpr-2.06'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: rlpr
Source-Version: 2.06-3
Done: Thorsten Alteholz <debian@alteholz.de>

We believe that the bug you reported is fixed in the latest version of
rlpr, 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 1097795@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 rlpr 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:03:02 +0200
Source: rlpr
Architecture: source
Version: 2.06-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Changed-By: Thorsten Alteholz <debian@alteholz.de>
Closes: 1097795
Changes:
 rlpr (2.06-3) unstable; urgency=medium
 .
   * debian/control: bump standard to 4.7.2 (no changes)
   * add gcc15.patch (Closes: #1097795)
Checksums-Sha1:
 ecb7cc20b4a20feb064e0ebe4cb6b235d0e5d14f 1969 rlpr_2.06-3.dsc
 3b14ca164033d529eb8fd6e781301ac93cdf00fd 272200 rlpr_2.06.orig.tar.gz
 cde3a44f8e182c9206c96a999b5ec5545983e530 7168 rlpr_2.06-3.debian.tar.xz
 b15927ad05b0da14f4e2ee5838fb8a7788235bde 6141 rlpr_2.06-3_amd64.buildinfo
Checksums-Sha256:
 064fe0facd008a0c52bf7fc0869c3e94be55b6f861513d8c8163bf08fb4da528 1969 rlpr_2.06-3.dsc
 32ae5893f4b9250b7a02c98a41b5929cfdd5731b6efbd7edfc77c2c5314388f7 272200 rlpr_2.06.orig.tar.gz
 d729302070d3f5a52e60bc2e759a3df462d37fca069ea65bbda4d08d8c9eec47 7168 rlpr_2.06-3.debian.tar.xz
 0e8fbd931b8133cb4a02899ae0269a086dcc1b30c79f8decc523b12a985be4ab 6141 rlpr_2.06-3_amd64.buildinfo
Files:
 2a62034fa44b09ad38045bea88f1627c 1969 net optional rlpr_2.06-3.dsc
 c3192d0e84ccae432e754640f6003478 272200 net optional rlpr_2.06.orig.tar.gz
 2ba33da3153c5b47d2eab2799b8a54b7 7168 net optional rlpr_2.06-3.debian.tar.xz
 c954a627bcb681dc9448683dccebc540 6141 net optional rlpr_2.06-3_amd64.buildinfo

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

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmjIicBfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYRz1iD/47/1ypGoRwBLDmNxjrfQvav53QPZ7r
MWiBWhzpBCjLmOKV+vh6xoC7+f1DDb5mCeQ26mn4n+Re0KVNvGEmv/IQPhuy4TZm
pSjMJH1SfBbflOeAe0E6gSzrDSs0BinKf6m/NkqgQz2J38se6aoogpdmdjpGy46+
u0nBP8TF3lbUY+o2TOYVt6bcVnvu8O0cI7BMvTPtW/MM8AWzaADM6vVNB5WmL6ca
HcTxJo0x6C7gs5HbtXsTlS+QzmH1E5x8YQPbXDdl+4g+xBBj+gl90v+LKbsW2vQx
K61ZCHvuqo7r2YLDZahmWXNyr90gvJdHWKB7JXDqDio/8O/2gIZrK9qROaNaxmV0
oCtETA1IaIrDT+9EWLiKHZNcPzMC7fN/+GZQI7UFD9JyXyGpzBULfWnVsU18AUbH
xGeNf/xqKxlsay8Af81mQuyNPsCxq8QSV4BKq5YJBT03+amAkP6FrSI5dH7669Je
UBaksJGtSQMrUtb3lgUTMXJlGWrAVLma9J9ivr2YNgFm0T2VnvP3X3rwrcXuK/2h
GqcvcHs/OR8RbF54i8E20KTWD6ZhlJKYSSArMMvUTVYnlRvlrN++Ps3EJDDmW/n3
Y0UvAOGzDaFnTJNpQj2gXzRolk0t0b8D2eByIA9bA80GWWgiOHmbRxTLEcas3cZR
et0mg4wvdp+FBQ==
=LQDR
-----END PGP SIGNATURE-----

Attachment: pgpD4oM6qD76v.pgp
Description: PGP signature


--- End Message ---
Reply to: