Your message dated Sun, 07 Jul 2024 18:21:46 +0000
with message-id <e1sqwwa-000igo...@fasolo.debian.org>
and subject line Bug#1075272: fixed in mig 1.8+git20231217-2
has caused the Debian Bug report #1075272,
regarding mig: ftbfs with GCC-14
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.)


-- 
1075272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mig
Version: 1.8+git20231217-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is 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-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/mig_1.8+git20231217-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

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-14/porting_to.html

[...]
ERROR: Could not compile stubs for routine
FAIL routine.defs (exit status: 1)

FAIL: types
===========

Generating stubs for types...
Compiling stubs for types...
types-user.c: In function ‘alltypes’:
types-user.c:274:37: error: implicit declaration of function 
‘mig_get_reply_port’; did you mean ‘msgh_reply_port’? 
[-Wimplicit-function-declaration]
  274 |         InP->Head.msgh_reply_port = mig_get_reply_port();
      |                                     ^~~~~~~~~~~~~~~~~~
      |                                     msgh_reply_port
types-user.c:283:17: error: implicit declaration of function 
‘mig_dealloc_reply_port’ [-Wimplicit-function-declaration]
  283 |                 mig_dealloc_reply_port(InP->Head.msgh_reply_port);
      |                 ^~~~~~~~~~~~~~~~~~~~~~
types-user.c:286:9: error: implicit declaration of function 
‘mig_put_reply_port’; did you mean ‘msgh_reply_port’? 
[-Wimplicit-function-declaration]
  286 |         mig_put_reply_port(InP->Head.msgh_reply_port);
      |         ^~~~~~~~~~~~~~~~~~
      |         msgh_reply_port
ERROR: Could not compile stubs for types
FAIL types.defs (exit status: 1)

FAIL: waittime
==============

Generating stubs for waittime...
Compiling stubs for waittime...
waittime-user.c: In function ‘factorial’:
waittime-user.c:119:37: error: implicit declaration of function 
‘mig_get_reply_port’; did you mean ‘msgh_reply_port’? 
[-Wimplicit-function-declaration]
  119 |         InP->Head.msgh_reply_port = mig_get_reply_port();
      |                                     ^~~~~~~~~~~~~~~~~~
      |                                     msgh_reply_port
waittime-user.c:128:17: error: implicit declaration of function 
‘mig_dealloc_reply_port’ [-Wimplicit-function-declaration]
  128 |                 mig_dealloc_reply_port(InP->Head.msgh_reply_port);
      |                 ^~~~~~~~~~~~~~~~~~~~~~
waittime-user.c:131:9: error: implicit declaration of function 
‘mig_put_reply_port’; did you mean ‘msgh_reply_port’? 
[-Wimplicit-function-declaration]
  131 |         mig_put_reply_port(InP->Head.msgh_reply_port);
      |         ^~~~~~~~~~~~~~~~~~
      |         msgh_reply_port
ERROR: Could not compile stubs for waittime
FAIL waittime.defs (exit status: 1)

============================================================================
Testsuite summary for GNU MIG 1.8+git20231217
============================================================================
# TOTAL: 7
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  6
# XPASS: 0
# ERROR: 0
============================================================================
See tests/good/test-suite.log
Please report to bug-h...@gnu.org
============================================================================
make[5]: *** [Makefile:541: test-suite.log] Error 1
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/tests/good'
make[4]: *** [Makefile:649: check-TESTS] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/tests/good'
make[3]: *** [Makefile:714: check-am] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/tests/good'
make[2]: *** [Makefile:335: check-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build/tests'
make[1]: *** [Makefile:593: check-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>/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-2
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 1075...@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: Sun, 07 Jul 2024 20:02:52 +0200
Source: mig
Architecture: source
Version: 1.8+git20231217-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Hurd Maintainers <debian-hurd@lists.debian.org>
Changed-By: Samuel Thibault <sthiba...@debian.org>
Closes: 1075272
Changes:
 mig (1.8+git20231217-2) unstable; urgency=medium
 .
   * rules: Fix taking target compilation flags.
   * patches/implicit-declaration: Fix build with gcc-14 (Closes: Bug#1075272)
Checksums-Sha1:
 2c01b099b7ca6cc1a741f92aa0f43c6055d1d183 2295 mig_1.8+git20231217-2.dsc
 3b33fdfb0e781b4fa25fd67661001c38c44a125c 9724 
mig_1.8+git20231217-2.debian.tar.xz
 8b35f0673f44e51ab5a9424435d991048f9a2192 7388 
mig_1.8+git20231217-2_source.buildinfo
Checksums-Sha256:
 3137ccd32eff1c4b4a213f710fa2c1e813d973b2e1347990f07cae145ed2a21f 2295 
mig_1.8+git20231217-2.dsc
 b8215a031d331844185363f7d7cbde87ae0ac40bed48a1071a21ba98cf9da344 9724 
mig_1.8+git20231217-2.debian.tar.xz
 a0c3270d17cac6959bb7bcd2539d952904aecc94b4a1e17ebb05f82504242294 7388 
mig_1.8+git20231217-2_source.buildinfo
Files:
 796eadb14b077368a5d4baa195d3cb76 2295 devel optional mig_1.8+git20231217-2.dsc
 9c6c042d5446bba8a3e64e94d159b2dc 9724 devel optional 
mig_1.8+git20231217-2.debian.tar.xz
 015647ecda1f84963d82248f321d2348 7388 devel optional 
mig_1.8+git20231217-2_source.buildinfo

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

iQJJBAEBCgAzFiEEqpLrvfAUiqYaQ7iu5IlMrEVBS7AFAmaK2vsVHHN0aGliYXVs
dEBkZWJpYW4ub3JnAAoJEOSJTKxFQUuwNqMQAJPDM6zfA8U/CO9brKYVMXqjXX5v
JuDUswd9jVyJDa609uBv3lY4YoJQ+sUF188MHQj3GIgw9FrR2yIfR2OTG/md/oKT
ynG+itK0zmt+1C/Y5w22NcKkViLAe/VFAKz/Ug2sRqlnftl0NhUp6Tb0PMlEP+Zl
MiwEUCmtPwfz64bbNafJgGof+V5wnKj6RR22+FgYTsIN1SD1oxRmT8JxDk3VUSU3
Zw703jF9AHZMFOzq8FzfgYEq8VGwWRMJnnqD+Xec9rsl5q1M7g41CIOBgvEChcOU
wy91LQjWTnNCczUJ7ElqTYS9G1pFElIG2b6tW30+yJnPxin+KOH/+RTy/S+T0o22
TMETim5S3klxEyoWcHWKzaIXaQ/BvIGXXZiBhukT2A3sOC/HCMsTf9ntk7xY09R2
sX0i/3vSmmB7tBnMKLMFGPB4KbiPHWeeUQvrDAnpYZkYQHRatLODPDzn98/NwgZK
TZbvREjYesqNSkxGfWgbV3Zqwl8xhdRfGqWFGV67FT02VAc6jOYVplDGY5m6C7OX
a4UCUfho5hjQ4lS//69dwumZ6AHrN+VJXAEOMgKyOG3mfCJI0f7h/y0JlvHwLpQ/
SCQbJZ7tFSLOzCgesROsmr9U1iLhANNp9bWOINMxOtqEToOfnGfR2L14596y8p8H
Z5nnE2LrRFhacNa9
=XKhw
-----END PGP SIGNATURE-----

Attachment: pgpsmg8RtRK7K.pgp
Description: PGP signature


--- End Message ---

Reply via email to