Your message dated Sat, 23 Aug 2025 15:52:38 +0000
with message-id <[email protected]>
and subject line Bug#1097415: fixed in motif 2.3.8-5
has caused the Debian Bug report #1097415,
regarding motif: 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 [email protected]
immediately.)
--
1097415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097415
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:motif
Version: 2.3.8-4
Severity: important
Tags: sid forky
User: [email protected]
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/motif_2.3.8-4_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
[...]
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:243:43: note: (near initialization for ‘headerproc[4]’)
makestrs.c:133:1: note: ‘SPARCABIWriteHeader’ declared here
133 | SPARCABIWriteHeader (FILE* f, File* phile)
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:243:64: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(FILE *, File *)’ {aka ‘void (*)(FILE *, struct _File
*)’} [-Wincompatible-pointer-types]
243 | SPARCABIWriteHeader,
FunctionWriteHeader };
|
^~~~~~~~~~~~~~~~~~~
makestrs.c:243:64: note: (near initialization for ‘headerproc[5]’)
makestrs.c:145:1: note: ‘FunctionWriteHeader’ declared here
145 | FunctionWriteHeader (FILE* f, File* phile)
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:270:6: error: too many arguments to function ‘headerproc[abi]’;
expected 0, have 2
270 | (*headerproc[abi])(f, phile);
| ~^~~~~~~~~~~~~~~~~ ~
makestrs.c: In function ‘WriteSource’:
makestrs.c:408:9: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
408 | DefaultWriteSource, ArrayperWriteSource,
| ^~~~~~~~~~~~~~~~~~
makestrs.c:408:9: note: (near initialization for ‘sourceproc[0]’)
makestrs.c:386:1: note: ‘DefaultWriteSource’ declared here
386 | DefaultWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~
makestrs.c:408:29: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
408 | DefaultWriteSource, ArrayperWriteSource,
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:408:29: note: (near initialization for ‘sourceproc[1]’)
makestrs.c:363:1: note: ‘ArrayperWriteSource’ declared here
363 | ArrayperWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:409:9: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
409 | IntelABIWriteSource, IntelABIBCWriteSource,
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:409:9: note: (near initialization for ‘sourceproc[2]’)
makestrs.c:293:1: note: ‘IntelABIWriteSource’ declared here
293 | IntelABIWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:409:30: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
409 | IntelABIWriteSource, IntelABIBCWriteSource,
| ^~~~~~~~~~~~~~~~~~~~~
makestrs.c:409:30: note: (near initialization for ‘sourceproc[3]’)
makestrs.c:312:1: note: ‘IntelABIBCWriteSource’ declared here
312 | IntelABIBCWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~~~~
makestrs.c:410:9: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
410 | DefaultWriteSource, FunctionWriteSource };
| ^~~~~~~~~~~~~~~~~~
makestrs.c:410:9: note: (near initialization for ‘sourceproc[4]’)
makestrs.c:386:1: note: ‘DefaultWriteSource’ declared here
386 | DefaultWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~
makestrs.c:410:29: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
410 | DefaultWriteSource, FunctionWriteSource };
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:410:29: note: (near initialization for ‘sourceproc[5]’)
makestrs.c:340:1: note: ‘FunctionWriteSource’ declared here
340 | FunctionWriteSource (int abi)
| ^~~~~~~~~~~~~~~~~~~
makestrs.c:433:6: error: too many arguments to function ‘sourceproc[abi]’;
expected 0, have 1
433 | (*sourceproc[abi])(abi);
| ~^~~~~~~~~~~~~~~~~ ~~~
make[3]: *** [Makefile:414: makestrs.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/motif-2.3.8/config/util'
make[2]: *** [Makefile:402: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/motif-2.3.8/config'
make[1]: *** [Makefile:464: all-recursive] Error 1
make[1]: Leaving directory '/build/reproducible-path/motif-2.3.8'
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: motif
Source-Version: 2.3.8-5
Done: Graham Inggs <[email protected]>
We believe that the bug you reported is fixed in the latest version of
motif, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Graham Inggs <[email protected]> (supplier of updated motif 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 23 Aug 2025 15:11:10 +0000
Source: motif
Built-For-Profiles: noudeb
Architecture: source
Version: 2.3.8-5
Distribution: unstable
Urgency: medium
Maintainer: Graham Inggs <[email protected]>
Changed-By: Graham Inggs <[email protected]>
Closes: 1097415
Changes:
motif (2.3.8-5) unstable; urgency=medium
.
* Build with -std=gnu17 to avoid FTBFS with GCC 15
(Closes: #1097415)
* Use the same flags during the autopkgtest
* Update debian/copyright
* Bump Standards-Version to 4.7.2, no changes
Checksums-Sha1:
9ca4a44c686eb36f9fa2df40a199d24d05073a7a 2409 motif_2.3.8-5.dsc
14eca63d52f51cd370183f45a3865927165dc5e0 52352 motif_2.3.8-5.debian.tar.xz
Checksums-Sha256:
2eeb399ad93fdb29dfb8254c41649cf198d5d26e362a02320b8bc8796cddbe1a 2409
motif_2.3.8-5.dsc
e96ad0c4591697940cc44b66b96198cf792c7745b09acff96d6d1f8dc90d0060 52352
motif_2.3.8-5.debian.tar.xz
Files:
b8eb02c213b6b10e3fb555dc2ac901bb 2409 x11 optional motif_2.3.8-5.dsc
0603d196958a5fcdeef39d759c283f25 52352 x11 optional motif_2.3.8-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmip2uAACgkQr8/sjmac
4cJQyg//cJ/8+mnMcuVWxobNA8mSP5BmDKk6DAVtIPcvxd2NV8ZFIM5ThLiGwVbl
ukmvm5bLZtNT5IlAYknHc7uygfYICXMuGybOQ6HG6xBRRxhIZgOIY3L++3grZizn
gAjNUOINlLeGCJo4esJqJxozqA3v2RO5PrJV5IeHy0TPl1gygB8Vj9Pq4Sj5tziQ
DHYU6htxQp+N/aqmXe24A3JvSuFDFQ5kxfXKjJrYRC54yCVOsv0k2jcQpo5ZQKMb
N8HER9RQZ3GaORvEpG4v3dvGlCJASTQpGbjvMUobOpWWsS0fVrsi179Z6z8xJEmG
zzE2DrntHlbAnvkNqjLWArxHGt42V3DYVfxtlh6vAB3Rg38ahiN2RBns7oj13SUw
EsOB5RFrFC28SEQX8T5fTkVnm64j0/0f+1046DsHFb51nLrWXTO1rEZ1tNvrMccD
D15kE9SFLbKC4edGR1j79O2VZhZ1aulkgcCcB0VrcP8LIPQvlFOSde+MnqoYarxY
5QyadDdhbDiT/yBa40LKhXlYrGPRDaxHPzWkIAVqOjCpg+ykpkQ/3bBUc33NLSd+
S4Q923HUvtAcc4Xkbc6HaR8+aqVNkg6hiDtQhKI2johgy8H7X73iYHaegXYK3v7a
50sZdAWiAl2JRKGfgqynR7lMCil0m8I9M2haRgDB7jOsDSDKCHI=
=dl7R
-----END PGP SIGNATURE-----
pgp2CHkoXScNL.pgp
Description: PGP signature
--- End Message ---
