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

Bug#1097873: marked as done (seyon: ftbfs with GCC-15)

Your message dated Sat, 25 Oct 2025 09:37:56 +0000
with message-id <E1vCaii-00Dwyq-1G@fasolo.debian.org>
and subject line Bug#1097873: fixed in seyon 2.20c-37
has caused the Debian Bug report #1097873,
regarding seyon: 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.)


-- 
1097873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097873
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:seyon
Version: 2.20c-36
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/seyon_2.20c-36_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

[...]
   81 |                 SeErrorF(),
      |                 ^~~~~~~~
Seyon.c:385:5: error: too many arguments to function ‘SeNoticeF’; expected 0, have 4
  385 |     SeNoticeF("Debugging info: pid=%d.", getpid(), "", "");
      |     ^~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~
SeDecl.h:85:17: note: declared here
   85 |                 SeNoticeF(),
      |                 ^~~~~~~~~
Seyon.c:391:9: error: too many arguments to function ‘SeNotice’; expected 0, have 1
  391 |         SeNotice("Press any key to exit");
      |         ^~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~
SeDecl.h:84:17: note: declared here
   84 |                 SeNotice(),
      |                 ^~~~~~~~
Seyon.c:393:9: error: too many arguments to function ‘cleanup_exit’; expected 0, have 1
  393 |         cleanup_exit(1);
      |         ^~~~~~~~~~~~ ~
Seyon.c:61:17: note: declared here
   61 |                 cleanup_exit();
      |                 ^~~~~~~~~~~~
Seyon.c:396:9: error: too many arguments to function ‘write_child_info’; expected 0, have 3
  396 |         write_child_info(child_pipe, KILL_TERM, "Terminal Proc Exited");
      |         ^~~~~~~~~~~~~~~~ ~~~~~~~~~~
SeDecl.h:95:17: note: declared here
   95 |                 write_child_info(),
      |                 ^~~~~~~~~~~~~~~~
Seyon.c: At top level:
Seyon.c:402:1: error: conflicting types for ‘do_exit’; have ‘void(int)’
  402 | do_exit(int rc)
      | ^~~~~~~
SeDecl.h:124:17: note: previous declaration of ‘do_exit’ with type ‘void(void)’
  124 |                 do_exit(),
      |                 ^~~~~~~
Seyon.c:424:1: error: conflicting types for ‘cleanup_exit’; have ‘void(int)’
  424 | cleanup_exit(int status)
      | ^~~~~~~~~~~~
Seyon.c:61:17: note: previous declaration of ‘cleanup_exit’ with type ‘void(void)’
   61 |                 cleanup_exit();
      |                 ^~~~~~~~~~~~
Seyon.c: In function ‘cleanup_exit’:
Seyon.c:426:5: error: too many arguments to function ‘SeNotice’; expected 0, have 1
  426 |     SeNotice("cleaning up..");
      |     ^~~~~~~~ ~~~~~~~~~~~~~~~
SeDecl.h:84:17: note: declared here
   84 |                 SeNotice(),
      |                 ^~~~~~~~
Seyon.c: In function ‘s_exit’:
Seyon.c:433:5: error: too many arguments to function ‘show’; expected 0, have 1
  433 |     show("I'm rated PG-34!!");
      |     ^~~~ ~~~~~~~~~~~~~~~~~~~
SeDecl.h:69:17: note: declared here
   69 |                 show(),
      |                 ^~~~
Seyon.c: In function ‘main’:
Seyon.c:298:5: warning: ignoring return value of ‘pipe’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  298 |     pipe(child_pipe);
      |     ^~~~~~~~~~~~~~~~
Seyon.c:299:5: warning: ignoring return value of ‘pipe’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  299 |     pipe(scriptToMainPipe);
      |     ^~~~~~~~~~~~~~~~~~~~~~
Seyon.c:300:5: warning: ignoring return value of ‘pipe’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  300 |     pipe(mainToTermPipe);
      |     ^~~~~~~~~~~~~~~~~~~~
make[2]: *** [<builtin>: Seyon.o] Error 1
make[2]: Leaving directory '/build/reproducible-path/seyon-2.20c'
dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true" LOCAL_LDFLAGS=-Wl,-z,relro CDEBUGFLAGS= "CCOPTIONS=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/seyon-2.20c=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fcommon -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall" returned exit code 2
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/reproducible-path/seyon-2.20c'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: seyon
Source-Version: 2.20c-37
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
seyon, 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 1097873@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 seyon 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: Fri, 24 Oct 2025 22:35:37 +0300
Source: seyon
Architecture: source
Version: 2.20c-37
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1097873
Changes:
 seyon (2.20c-37) unstable; urgency=medium
 .
   * QA upload.
   * Build with -std=gnu17 to workaround FTBFS with GCC 15.
     (Closes: #1097873)
Checksums-Sha1:
 4ac543498eaa9447575151ccc04540f4c99adc84 1812 seyon_2.20c-37.dsc
 bebddc965ddc01365b140e3d68486ec3bbb58b83 37632 seyon_2.20c-37.debian.tar.xz
Checksums-Sha256:
 9dcab7f7903de12f687eb5302e735b5d91e6f74406e95c77314534eb67867f3b 1812 seyon_2.20c-37.dsc
 85057504075b1bbab2716f7111f70b4493a29f82d19eb476ce05719b45c5f4fc 37632 seyon_2.20c-37.debian.tar.xz
Files:
 ca62db04180eea98a805dc7e9f8c695f 1812 comm optional seyon_2.20c-37.dsc
 2e5b4cc06205faa217e95c1c17ffeceb 37632 comm optional seyon_2.20c-37.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmj8kz0ACgkQiNJCh6LY
mLGciQ//aZA/Lcdk0G03TgScgSuSrZ0HoJu2TaEctdVjI19EabH9QybTkyfilIch
sOOMvmtrO67nK9QPGuTyZHorS8Y8bV/2BPSfm/oBuOGjmE2Q+V6vJ3vO+r++nsUn
RkEyBXzbfq4W8OcJuVnYy5RRkVriEhdT14EC43sXJnL8s8kwQYyBJeJDDYI6gDjo
zFMCNIw0YrwqqUGLGn2HjtP9XytXiKbHzRWVNtEdtNk7xLlYFmVfLe23JwPTVR11
dTWwQflkbHtaPpZFdmsX9TCjKYTg/FxOIhBMIE6fEj2yZwh0olyoDuA6bpg6zhnn
jr2QsPLb8bdzg2L1i+5cyu0EL1DXo49yX2I7SQgYDA9llO+swlmRHgMYx8scQf+U
bF1zeeW5kP7OP1VR3A0I6ifwL0FrseTmwivIyrJmbtDFFziottnuHkQSSvbE5IYu
kqV+GKiC0ytxHQTTvOoRHh44K5GFBPbW4Gu5Qhj4O6gcYRPsiwMQyiaxJCFO7Iw3
2mEf9sEBpwUitgoeRM8el51gyoiaJAXrL5rSmvOGDmX9n1ljKQ375frID/v4eOcj
mUIXzYuOXlSyljUH4diDIHUGiBa5e6HvyTGrkIc2JWqCooagYOdWK7GAmQDtzLSQ
dEZG8AR4ntkCVL9ZW5x0wciGCb9Lq6C+FsmWj4v+zIVxCK8rCtg=
=in7g
-----END PGP SIGNATURE-----

Attachment: pgpmwWvoH5b94.pgp
Description: PGP signature


--- End Message ---
Reply to: