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

Bug#1096827: marked as done (icom: ftbfs with GCC-15)

Your message dated Mon, 08 Sep 2025 04:33:51 +0000
with message-id <E1uvTZf-00ClK4-31@fasolo.debian.org>
and subject line Bug#1096827: fixed in icom 20120228-7
has caused the Debian Bug report #1096827,
regarding icom: 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.)


-- 
1096827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096827
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:icom
Version: 20120228-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/icom_20120228-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

[...]
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2410:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2410 |                         strcpy(s2, "semi");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2412:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2412 |                         strcpy(s2, "full");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2425:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2425 |                         strcpy(s2, "off");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2427:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2427 |                         strcpy(s2, "1");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2429:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2429 |                         strcpy(s2, "2");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2434:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2434 |                         strcpy(s2, "open");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2436:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2436 |                         strcpy(s2, "closed");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2441:17: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2441 |                 strcpy(s2, mtab[i].pip);
      |                 ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2446:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2446 |                         strcpy(s2, "off");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
icom.c:2448:25: error: too many arguments to function ‘strcpy’; expected 0, have 2
 2448 |                         strcpy(s2, "on");
      |                         ^~~~~~ ~~
icom.c:29:25: note: declared here
   29 | extern char *strtok(), *strcpy();
      |                         ^~~~~~
make[1]: *** [<builtin>: icom.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/build/reproducible-path/icom-20120228'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:9: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: icom
Source-Version: 20120228-7
Done: tony mancill <tmancill@debian.org>

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

Debian distribution maintenance software
pp.
tony mancill <tmancill@debian.org> (supplier of updated icom 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: Sun, 07 Sep 2025 21:14:34 -0700
Source: icom
Architecture: source
Version: 20120228-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: tony mancill <tmancill@debian.org>
Closes: 1096827
Changes:
 icom (20120228-7) unstable; urgency=medium
 .
   * Address FTBFS with GCC-15 (Closes: #1096827)
   * Freshen patches
Checksums-Sha1:
 e8f33c83533693abeaf47954c2ed9123bbb154b7 1961 icom_20120228-7.dsc
 bb4e4870c628874f4f96feeb139650b2351ea00c 12528 icom_20120228-7.debian.tar.xz
 744c6cada2e9bb40df0be94ef10524680ca1e26a 5883 icom_20120228-7_amd64.buildinfo
Checksums-Sha256:
 ed27715681950c512c4a2a33e3d1b343a331b3ed941b35599faa1cd912b88376 1961 icom_20120228-7.dsc
 37a91a379824077a8058bd90d6c5f523a47ce01c7b6425a5c271f89d6fba3a28 12528 icom_20120228-7.debian.tar.xz
 47fb34c440fd1148342c729c2704036f2dfec3826260896a15ff14b140d73a4b 5883 icom_20120228-7_amd64.buildinfo
Files:
 ff309f45b35a80ba87aefaac8f2db9f8 1961 hamradio optional icom_20120228-7.dsc
 6c27afcc73a644eb555a7ddd6d7b32d8 12528 hamradio optional icom_20120228-7.debian.tar.xz
 c46f62b3e9d1f2f51be82d696f0ba720 5883 hamradio optional icom_20120228-7_amd64.buildinfo

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

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmi+WVQUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZqoRAAiNIcRypAWMdMQV0+3MBVuOAl9pCO
oikSyvQKDdZjgl8PPqomTLhKHEBIeR6O8c76LS66nXaCr5HCk5T0jH3fO07cuEj1
lHKDYfo4/6z3FjxCY3UL7AJk7468NLJCCAyBqSD8IeJRYigKUH3d8Owm6DMtHH6A
yuxczlHoEfz8Vtd9w8+TSezJpgF/mvtS3/Vkp4A59fbHHMt5Pn5mBKL40XmdgCoZ
YwtjFNckkkOisLt7g78wHi+jMWnmqlS2T7e6G2ULlawBkScz/Oh/bitiXDMwHZHH
uk/7YXNmWmzSBxC/xJwUXf3sc/xTu45H7K0o2bJVSg68hmb468X78QWgykC4pKSN
KKFnPfYSCuK9roKM+hVEyQskUB2GzOk6SMec+fAH2QjCoj3NHJqN8J+kzsxffH1t
9oO2Hqrjx12H8T/CDHxKcGMKzmysf409LzHVrN19m3TQ+LT7MMp+4Va92HE4wNwO
rd5LGBhgajCTOx6uCTQEfUjbNp92gnHMA7NOLsXW36u19y21n2oS5NsYESfyiR+4
aB50yM6VFUXpHiL2ibhEcBdv4fM1g5E5uQSnke3xvoSbT4gP5OGt/aedZkD6VuCk
izvHc3a1teL3FZmfpOCFZCAqX9NgRyE0Bwj6FslDHcMAJXViMopfHL7R7Yj3lxNb
USp7tCSjuYj24Qk=
=Iskx
-----END PGP SIGNATURE-----

Attachment: pgpgVsR09MlPQ.pgp
Description: PGP signature


--- End Message ---
Reply to: