Your message dated Mon, 31 Mar 2025 21:36:28 +0000
with message-id <e1tzmo0-001aql...@fasolo.debian.org>
and subject line Bug#1097397: fixed in mig 1.8+git20231217-6
has caused the Debian Bug report #1097397,
regarding mig: 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 ow...@bugs.debian.org
immediately.)
--
1097397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mig
Version: 1.8+git20231217-5
Severity: important
Tags: sid forky
User: debian-...@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/mig_1.8+git20231217-5_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: 0
System information (uname -a): Linux 6.1.0-28-cloud-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64
Distribution information (/etc/os-release):
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";
.. contents:: :depth: 2
FAIL: types
===========
Generating stubs for types...
Compiling stubs for types...
types-server.c: In function ‘_Xalltypes’:
types-server.c:70:27: error: two or more data types in declaration specifiers
70 | boolean_t bool;
| ^~~~
types-server.c:70:31: warning: declaration does not declare anything
70 | boolean_t bool;
| ^
types-server.c:92:109: error: two or more data types in declaration specifiers
92 | (mach_port_t port, char c, int16_t s1, short s2, int i,
int32_t i32, int64_t i64, boolean_t bool, uint16_t ui16, uint32_t ui32,
uint64_t ui64);
|
^~~~
types-server.c:250:130: error: expected identifier before ‘bool’
250 | OutP->RetCode = alltypes(In0P->Head.msgh_request_port, In0P->c,
In0P->s1, In0P->s2, In0P->i, In0P->i32, In0P->i64, In0P->bool, In0P->ui16,
In0P->ui32, In0P->ui64);
|
^~~~
types-server.c:250:25: error: too few arguments to function ‘alltypes’;
expected 11, have 8
250 | OutP->RetCode = alltypes(In0P->Head.msgh_request_port, In0P->c,
In0P->s1, In0P->s2, In0P->i, In0P->i32, In0P->i64, In0P->bool, In0P->ui16,
In0P->ui32, In0P->ui64);
| ^~~~~~~~
types-server.c:91:36: note: declared here
91 | mig_external kern_return_t alltypes
| ^~~~~~~~
ERROR: Could not compile stubs for types
FAIL types.defs (exit status: 1)
============================================================================
Testsuite summary for GNU MIG 1.8+git20231217
============================================================================
# TOTAL: 7
# PASS: 6
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/good/test-suite.log for debugging.
Some test(s) failed. Please report this to bug-h...@gnu.org,
together with the test-suite.log file (gzipped) and your system
information. Thanks.
============================================================================
make[5]: *** [Makefile:549: test-suite.log] Error 1
make[5]: Leaving directory
'/build/reproducible-path/mig-1.8+git20231217/build/tests/good'
make[4]: *** [Makefile:684: check-TESTS] Error 2
make[4]: Leaving directory
'/build/reproducible-path/mig-1.8+git20231217/build/tests/good'
make[3]: *** [Makefile:748: check-am] Error 2
make[3]: Leaving directory
'/build/reproducible-path/mig-1.8+git20231217/build/tests/good'
make[2]: *** [Makefile:339: check-recursive] Error 1
make[2]: Leaving directory
'/build/reproducible-path/mig-1.8+git20231217/build/tests'
make[1]: *** [Makefile:598: check-recursive] Error 1
make[1]: Leaving directory '/build/reproducible-path/mig-1.8+git20231217/build'
dh_auto_test: error: cd build && make -j8 check "TESTSUITEFLAGS=-j8 --verbose"
VERBOSE=1 returned exit code 2
make: *** [debian/rules:16: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: mig
Source-Version: 1.8+git20231217-6
Done: Samuel Thibault <sthiba...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mig, 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 1097...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault <sthiba...@debian.org> (supplier of updated mig 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 31 Mar 2025 23:18:47 +0200
Source: mig
Architecture: source
Version: 1.8+git20231217-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Hurd Maintainers <debian-hurd@lists.debian.org>
Changed-By: Samuel Thibault <sthiba...@debian.org>
Closes: 1097397
Changes:
mig (1.8+git20231217-6) unstable; urgency=medium
.
* control: Generalize mig and mig-for-host on all archs.
* patches/string_t: Ensure that strings in the request are null terminated
before calling the server routine.
* patches/gcc-15: Fix build with gcc-15 (Closes: Bug#1097397)
Checksums-Sha1:
5063c88b49a799d4355393f5c8c37f35056ec76d 2295 mig_1.8+git20231217-6.dsc
fd8112e7a1b889c8cc1c623186860fd83e7a82dc 11324
mig_1.8+git20231217-6.debian.tar.xz
fb79d811e06bcbca38534bdd832289f1c89f8669 6394
mig_1.8+git20231217-6_amd64.buildinfo
Checksums-Sha256:
5cbe3852dd82a6da252d31d440e28b890af14a285bcae3da1fde83c1a611515f 2295
mig_1.8+git20231217-6.dsc
ed6e84a83d5904af0a2c91c8cacd2b055bdd5dc545135f449c65c1fcdf25e239 11324
mig_1.8+git20231217-6.debian.tar.xz
c36bb09fd1e31a64a493411c257c97b0d5900c5884d9623a9a6a53d95a89b67e 6394
mig_1.8+git20231217-6_amd64.buildinfo
Files:
afee39655b375a299f3c9770fd6de1f2 2295 devel optional mig_1.8+git20231217-6.dsc
d637500171d6963906994abdc5dd329f 11324 devel optional
mig_1.8+git20231217-6.debian.tar.xz
a1101135bdf66da2a407bd17f2400864 6394 devel optional
mig_1.8+git20231217-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmfrBugACgkQaHTOWK4t
fj9XSw/8CrW/w2gbDWufnSOT46dsKK3zlX9SXh6scJ8T70w3FcpCrynTiv1kSFIb
TvPjSlvfo+1FJGR/4SmOrqHZBj4deMd0sl2F1VPor+w+o4L84iaOBWPfAu7rdxO9
AJvrDDwVSQmmbAbWTa1VqvvDa4++YDXvpoFZE2C7UKmeQea4KS5Qxea19pRvUoer
SyTSU97W/pZ1KQfk+otgtwDb6mX7HmMWxAVFn6hcBl9s8v+gIv1YI4p5DeiifyRc
xNmfr7rIx1+PN331aQy0qEFoje9tkjEhvpMUMEpgdJ0IHtzMWokpJsyr5dKpOPaV
QmGsZ4D8Xpcd8OiEahJbEghCF5Yk9nqdIGx4CglHTrKMN3egQ2wHX+ArMtFyn5dW
ngloM/1BSiaY6Z3RmXadSwvuEIEo2KAkPiLZhluDEveOydCi7tkddEEbbNuGgMig
b4SVRmy/L5xzYJ7TTEhaNcGoOo6ZoGEdEjLnbI/10jL/iJ9qCf85Rxj9EXrteS7y
poTK4rhPO0MyH6aiF8yWqez/PJDzROTVzCsYbYu1yb5xnv5VpzG+AUvlJY4TlTNH
07lbLIkDg2MsgKunzrhy0SYkEhQjExsnS/xtiSs2HJ7TLtCOMYXWmx7kW8OgzHEO
kEG/zx0D5cZaWU+kaWa7eAOeoUrvYkL1OTZgjYoLsNPoGB7lAs4=
=41Bf
-----END PGP SIGNATURE-----
pgptthG4c5KSg.pgp
Description: PGP signature
--- End Message ---
