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

Bug#1097858: marked as done (scm: ftbfs with GCC-15)

Your message dated Sun, 09 Nov 2025 17:06:58 +0000
with message-id <E1vI8sU-0053DF-0G@fasolo.debian.org>
and subject line Bug#1097858: fixed in scm 5f4-3.1
has caused the Debian Bug report #1097858,
regarding scm: 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.)


-- 
1097858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097858
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:scm
Version: 5f4-3
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/scm_5f4-3_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

[...]
      |                ^~~~~~~~~~~~~~
scm.c: In function ‘scm_init_from_argv’:
scm.c:670:6: warning: old-style function definition [-Wold-style-definition]
  670 | void scm_init_from_argv(argc, argv, script_arg, iverbose, buf0stdin)
      |      ^~~~~~~~~~~~~~~~~~
scm.c: In function ‘final_scm’:
scm.c:692:6: warning: old-style function definition [-Wold-style-definition]
  692 | void final_scm(freeall)
      |      ^~~~~~~~~
scm.c: In function ‘init_buf0’:
scm.c:826:5: warning: old-style function definition [-Wold-style-definition]
  826 | int init_buf0(inport)
      |     ^~~~~~~~~
scm.c: In function ‘scm_execpath’:
scm.c:863:5: warning: old-style function definition [-Wold-style-definition]
  863 | SCM scm_execpath(newpath)
      |     ^~~~~~~~~~~~
scm.c: In function ‘scm_find_execpath’:
scm.c:882:7: warning: old-style function definition [-Wold-style-definition]
  882 | char *scm_find_execpath(argc, argv, script_arg)
      |       ^~~~~~~~~~~~~~~~~
scm.c: In function ‘lsystem’:
scm.c:922:5: warning: old-style function definition [-Wold-style-definition]
  922 | SCM lsystem(cmd)
      |     ^~~~~~~
scm.c: At top level:
scm.c:940:7: error: conflicting types for ‘getenv’; have ‘char *(void)’
  940 | char *getenv();
      |       ^~~~~~
In file included from scmfig.h:813,
                 from scm.h:65,
                 from scm.c:26:
/usr/include/stdlib.h:773:14: note: previous declaration of ‘getenv’ with type ‘char *(const char *)’
  773 | extern char *getenv (const char *__name) __THROW __nonnull ((1)) __wur;
      |              ^~~~~~
scm.c: In function ‘scm_getenv’:
scm.c:941:5: warning: old-style function definition [-Wold-style-definition]
  941 | SCM scm_getenv(nam)
      |     ^~~~~~~~~~
scm.c:958:9: error: too many arguments to function ‘getenv’; expected 0, have 1
  958 |   val = getenv(CHARS(nam));
      |         ^~~~~~
scm.c:940:7: note: declared here
  940 | char *getenv();
      |       ^~~~~~
scm.c: In function ‘add_feature’:
scm.c:1025:6: warning: old-style function definition [-Wold-style-definition]
 1025 | void add_feature(str)
      |      ^~~~~~~~~~~
scm.c: In function ‘init_features’:
scm.c:1036:36: error: passing argument 3 of ‘make_subr’ from incompatible pointer type [-Wincompatible-pointer-types]
 1036 |   make_subr(s_getenv, tc7_subr_1o, scm_getenv);
      |                                    ^~~~~~~~~~
      |                                    |
      |                                    SCM (*)(SCM) {aka long int (*)(long int)}
scm.h:816:64: note: expected ‘SCM (*)(void)’ {aka ‘long int (*)(void)’} but argument is of type ‘SCM (*)(SCM)’ {aka ‘long int (*)(long int)’}
  816 | SCM_EXPORT SCM  make_subr P((const char *name, int type, SCM (*fcn)()));
      |                                                          ~~~~~~^~~~~~
scm.h:97:15: note: in definition of macro ‘P’
   97 | # define P(s) s
      |               ^
scm.c:941:5: note: ‘scm_getenv’ declared here
  941 | SCM scm_getenv(nam)
      |     ^~~~~~~~~~
make[2]: *** [Makefile:320: scm.o] Error 1
make[2]: Leaving directory '/build/reproducible-path/scm-5f4'
make[1]: *** [debian/rules:32: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/reproducible-path/scm-5f4'
make: *** [debian/rules:19: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: scm
Source-Version: 5f4-3.1
Done: Adrian Bunk <bunk@debian.org>

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

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated scm 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: Sat, 25 Oct 2025 18:54:34 +0300
Source: scm
Architecture: source
Version: 5f4-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Scheme Dream Team <debian-scheme@lists.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1097858
Changes:
 scm (5f4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build with -std=gnu17 to workaround FTBFS with GCC 15.
     (Closes: #1097858)
Checksums-Sha1:
 2bd5274a45d81bfa7b5c07c3c70c4fa089d0740b 2282 scm_5f4-3.1.dsc
 b8f554926f0489dd2eb77f9e6e05c3ca25b7e551 21240 scm_5f4-3.1.debian.tar.xz
Checksums-Sha256:
 47c8e8ea1d2e341500e7e44328e8a1051a4eafb69c7005cc053c482f18de3ca6 2282 scm_5f4-3.1.dsc
 30be7df44852dcb90ea54abd9ca62be9e86e5954593873a58bd5aea6b1313c39 21240 scm_5f4-3.1.debian.tar.xz
Files:
 1afd5295e5aebb5f9e7183027997142c 2282 interpreters optional scm_5f4-3.1.dsc
 8159e7ffa3a71d4952b2dddc510d64c0 21240 interpreters optional scm_5f4-3.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmj89eEACgkQiNJCh6LY
mLGwRA/8CTatrcpBIwdFzWErUJgNpOl99wi/rmZ9cXG2GLCF7QFgK6DXIhkjN92X
YgNKaTvTiDjEYLDVNaz3IPa15C6WhhfHbmFuz4Aiom3C41SAwWBHQSq313dOXGZR
GlBuzfokBLUqNhjN4a/dTZlquEFq8pNc60cmq5ZzC7yjQBLoqSxfi0lKHoMNL8C/
xRVw7abgO1WPmGAYfVGNg/tlf8lyUVe1DYKL8R8WL39sLuPhXX+Y1sBFzonjBxsZ
/BJ6/6sLLe7KEwkrH/bsxYAR+Iz/BNenYeeLF9xsOxDo4eDdGQJYBoAGcJuhV2GX
XXcfnpfsBKE/X/Opoawu+58zJzMPP8PQpTVhp3XEhOcsRGBFnzmIcml4A19ca0mj
vFXhdJLAIPA3kBUVLEyQOlhvkB+bgXAFzQoZycJHuQl8xvm+2lehUVCekVLAKyt3
5Nyklh8R/Jol6pD1kF4g5pF/q3MX7diJEhzpyYzUnITZo4rTKKEsQZknm6UL+q7z
0d1AVE9KscAJCqlXaNE6ddTOId1ofix9xR+gxZLYtVkLO3GIPQnqbXKuxJLQIwHq
NmlLRjwPe4VCbYzkYUwqLzZZy9wW581wm4yTLCXP5dwudgxfpgrIwA2ivAYSG+Z6
Gm6eszc863Iw3R1cZhAk/E1LYKG/cVhsfkstUunBUQT2PsP635o=
=zwCw
-----END PGP SIGNATURE-----

Attachment: pgpZVJ0YFrT_1.pgp
Description: PGP signature


--- End Message ---
Reply to: