Your message dated Tue, 9 Sep 2025 21:13:59 +0200
with message-id <[email protected]>
and subject line eso-midas: ftbfs with GCC-15
has caused the Debian Bug report #1096587,
regarding eso-midas: 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.)


-- 
1096587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096587
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:eso-midas
Version: 23.02pl1.0-3
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/eso-midas_23.02pl1.0-3_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

[...]
esoext.c:89:38: note: declared here
   89 |   char    *f_name, *o_name, *table, *new_ext();
      |                                      ^~~~~~~
esoext.c:201:19: error: too many arguments to function ‘pop_fp’; expected 0, 
have 1
  201 |          if (!(fp=pop_fp(fp))) break;     /* if no include file         
 */
      |                   ^~~~~~ ~~
esoext.c:93:35: note: declared here
   93 |   FILE    *fp, *ofp, *push_fp(), *pop_fp();
      |                                   ^~~~~~
esoext.c:258:13: error: too many arguments to function ‘get_line’; expected 0, 
have 1
  258 |         c = get_line(fp);
      |             ^~~~~~~~ ~~
esoext.c:91:37: note: declared here
   91 |   char    *p,cont, *plab, label[6], get_line();
      |                                     ^~~~~~~~
esoext.c:263:20: error: too many arguments to function ‘line_type’; expected 0, 
have 1
  263 |           action = line_type(&stype);
      |                    ^~~~~~~~~ ~~~~~~
esoext.c:87:44: note: declared here
   87 |   int     c, ns, n, i, stype, action, nip, line_type();
      |                                            ^~~~~~~~~
esoext.c:265:25: error: too many arguments to function ‘incl_file’; expected 0, 
have 1
  265 |             incl_name = incl_file(stmt);
      |                         ^~~~~~~~~ ~~~~
esoext.c:90:44: note: declared here
   90 |   char    *incl_path[MXINCP], *incl_name, *incl_file();
      |                                            ^~~~~~~~~
esoext.c:268:18: error: too many arguments to function ‘push_fp’; expected 0, 
have 3
  268 |             fp = push_fp(fp,incl_path,incl_name);
      |                  ^~~~~~~ ~~
esoext.c:93:23: note: declared here
   93 |   FILE    *fp, *ofp, *push_fp(), *pop_fp();
      |                       ^~~~~~~
esoext.c:269:20: error: too many arguments to function ‘push_lab’; expected 0, 
have 1
  269 |             plab = push_lab(plab);
      |                    ^~~~~~~~ ~~~~
esoext.c:92:12: note: declared here
   92 |   char    *push_lab(), *pop_lab(), *new_file();
      |            ^~~~~~~~
esoext.c:276:13: error: too many arguments to function ‘put_line’; expected 0, 
have 4
  276 |             put_line(ofp,action,stype,labno);
      |             ^~~~~~~~ ~~~
esoext.c:88:27: note: declared here
   88 |   int     hstat[MXFSTAT], put_line(), labno,chk_id();
      |                           ^~~~~~~~
esoext.c:295:11: error: too many arguments to function ‘get_line’; expected 0, 
have 1
  295 |       c = get_line(fp);
      |           ^~~~~~~~ ~~
esoext.c:91:37: note: declared here
   91 |   char    *p,cont, *plab, label[6], get_line();
      |                                     ^~~~~~~~
esoext.c:300:16: error: too many arguments to function ‘line_type’; expected 0, 
have 1
  300 |       action = line_type(&stype);
      |                ^~~~~~~~~ ~~~~~~
esoext.c:87:44: note: declared here
   87 |   int     c, ns, n, i, stype, action, nip, line_type();
      |                                            ^~~~~~~~~
esoext.c:301:7: error: too many arguments to function ‘put_line’; expected 0, 
have 4
  301 |       put_line(ofp,action,stype,labno);
      |       ^~~~~~~~ ~~~
esoext.c:88:27: note: declared here
   88 |   int     hstat[MXFSTAT], put_line(), labno,chk_id();
      |                           ^~~~~~~~
make[2]: *** [../../local/default.mk:87: esoext.o] Error 1
make[2]: Leaving directory 
'/build/reproducible-path/eso-midas-23.02pl1.0/23FEB/system/ext'
Error building esoext.
make[1]: *** [debian/rules:33: override_dh_auto_build-arch] Error 1
make[1]: Leaving directory '/build/reproducible-path/eso-midas-23.02pl1.0'
make: *** [debian/rules:21: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Package: src:eso-midas
Version: 25.05pl1.1-1
Done: Ole Streicher <[email protected]>

This bug was fixed with the new upstream version; I just forgot to mention it in d/changelog.
--- End Message ---

Reply via email to