Your message dated Sat, 23 Aug 2025 19:05:38 +0000
with message-id <[email protected]>
and subject line Bug#1098182: fixed in yabasic 1:2.91.3-1
has caused the Debian Bug report #1098182,
regarding yabasic: 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.)


-- 
1098182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:yabasic
Version: 1:2.90.5-1
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/yabasic_2.90.5-1_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

[...]
checking for IceConnectionNumber in -lICE... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/reproducible-path/yabasic-2.90.5'
dh_auto_build -- bison flex
        make -j8 bison flex
make[2]: Entering directory '/build/reproducible-path/yabasic-2.90.5'
bison -d -l -t -v --output-file bison.c yabasic.bison
flex -i -I -L -s -d -t yabasic.flex >flex.c
make[2]: Leaving directory '/build/reproducible-path/yabasic-2.90.5'
make[1]: Leaving directory '/build/reproducible-path/yabasic-2.90.5'
   dh_auto_test
        make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1
make[1]: Entering directory '/build/reproducible-path/yabasic-2.90.5'
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o main.o main.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o function.o function.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o io.o io.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o graphic.o graphic.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o symbol.o symbol.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o foreign.o foreign.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o flow.o flow.c
gcc -DHAVE_CONFIG_H -I.  -DUNIX    -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/yabasic-2.90.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -c -o flex.o flex.c
graphic.c:1666:6: error: conflicting types for ‘moveorigin’; have ‘void(char *)’
 1666 | void moveorigin(char * or) {
      |      ^~~~~~~~~~
In file included from graphic.c:17:
yabasic.h:566:6: note: previous declaration of ‘moveorigin’ with type 
‘void(void)’
  566 | void moveorigin ();
      |      ^~~~~~~~~~
main.c: In function ‘run_it’:
main.c:1809:9: error: too many arguments to function ‘moveorigin’; expected 0, 
have 1
 1809 |         moveorigin(NULL);
      |         ^~~~~~~~~~ ~~~~
In file included from main.c:17:
yabasic.h:566:6: note: declared here
  566 | void moveorigin ();
      |      ^~~~~~~~~~
main.c:1862:9: error: too many arguments to function ‘poke’; expected 0, have 1
 1862 |         poke(currcmd);
      |         ^~~~ ~~~~~~~
yabasic.h:608:6: note: declared here
  608 | void poke ();
      |      ^~~~
function.c:1467:6: error: conflicting types for ‘poke’; have ‘void(struct 
command *)’
 1467 | void poke(struct command *cmd) /* poke into internals */
      |      ^~~~
In file included from function.c:17:
yabasic.h:608:6: note: previous declaration of ‘poke’ with type ‘void(void)’
  608 | void poke ();
      |      ^~~~
function.c: In function ‘poke’:
function.c:1508:5: error: too many arguments to function ‘moveorigin’; expected 
0, have 1
 1508 |     moveorigin(string_arg);
      |     ^~~~~~~~~~ ~~~~~~~~~~
yabasic.h:566:6: note: declared here
  566 | void moveorigin ();
      |      ^~~~~~~~~~
make[1]: *** [Makefile:707: graphic.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:707: main.o] Error 1
make[1]: *** [Makefile:707: function.o] Error 1
make[1]: Leaving directory '/build/reproducible-path/yabasic-2.90.5'
dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
returned exit code 2
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: yabasic
Source-Version: 1:2.91.3-1
Done: Graham Inggs <[email protected]>

We believe that the bug you reported is fixed in the latest version of
yabasic, 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 yabasic 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 18:35:12 +0000
Source: yabasic
Built-For-Profiles: noudeb
Architecture: source
Version: 1:2.91.3-1
Distribution: unstable
Urgency: medium
Maintainer: Graham Inggs <[email protected]>
Changed-By: Graham Inggs <[email protected]>
Closes: 1098182
Changes:
 yabasic (1:2.91.3-1) unstable; urgency=medium
 .
   * New upstream release
     - New peeks 'displayheight' and 'displaywidth' to
       get the resolution of your monitor.
     - Fix for option '--docu'
     - Fixed a bug with 'print reverse' under windows.
     - Documentation
   * Disable tests requiring tmux
   * Build with -std=gnu17 to avoid FTBFS with GCC 15
     (Closes: #1098182)
   * Bump Standards-Version to 4.7.2, no changes
Checksums-Sha1:
 d1f84d150c8961b7ea23cea54b5e676e0710839e 2017 yabasic_2.91.3-1.dsc
 2d3ce55b37e461addce7b00d4e7c8cc7d5d3f8a3 747852 yabasic_2.91.3.orig.tar.gz
 26baa2b9c7bc1b8c0b917f3c357d951ca8817de1 9044 yabasic_2.91.3-1.debian.tar.xz
Checksums-Sha256:
 cacc3eaed2904f6327f44385c61fb345e266237a37e6ae1fa151e4abfa58438f 2017 
yabasic_2.91.3-1.dsc
 fac4b791f5a13385b0af4486be4c7ce5e4e35f173d581bc45372745f2e0371fa 747852 
yabasic_2.91.3.orig.tar.gz
 c6e7b714768ae38e2c7dcce602b750d66aec1cc18ac0efe6b8db3c05605249bb 9044 
yabasic_2.91.3-1.debian.tar.xz
Files:
 a92495f53b04662c499dc109cc01d3ac 2017 interpreters optional 
yabasic_2.91.3-1.dsc
 1e9eb105f15cfe99c9df5142dd872701 747852 interpreters optional 
yabasic_2.91.3.orig.tar.gz
 c91585615bf70f7688fcaf89a52cf2be 9044 interpreters optional 
yabasic_2.91.3-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmiqCvQACgkQr8/sjmac
4cI7cQ//e+Iv6r8srcevyEfY4PDPnU434Clk8pVxkPHkI0GIyah6RnBmGhXkW9KU
guPxBHaFBjHAJrU7ZN2Axf3rpkK2QMPAnG3rg6yZAlakG/UozW5zGZRpdMco48/q
t1zBIK6bqvMqq2jn+1w8NEyQPYmDtCWHTB7ta9pqg4w0Mq+nfweePbarQwZrmo+3
3I26/b2qMYetMvwnxTZJA3/ls72+GeuFmZgZCtKp/1uCqE/U+lbgezwMOGsaAMxo
qdYeFKegRMra51SRKcIVZJnbFygpgpAPcexueEgjs8R4GsxcbgOhwPUxGQUgt0Zt
YfCiqQ82IKyyFyMuAV2j9Fj73u+oRsaCTM3Gfz0bvVCoPAKVonc77jA2sAp4ZZe4
sCpIwnOOFO0YK/WKh2DUfbhwBpWVjMfLiWc0pYpLJIwkLHYYsNBWiOOi0s2evOz2
Cg5x+j34zGHknD6NIKUex72VziEm6fY0o8bCh3WzqXxEQm3IEFXVr5QXONjlmzdN
oIhbz8ESMMxFuHdQaElEtzDXu19H6HI3peLH90JnoXOyGFYGZWZ2CMliowhba5j7
IeLbVX69eRKJ5Y2dyHDrUEU0ei64LNqvwhkmw2But9+Y675kgGHARIjNo2M8D+/G
IdiFxjpUjT6JoU7zuF5NvmTuJQznm8Y7MkdWkLQIAvdmvUP6ilg=
=J19y
-----END PGP SIGNATURE-----

Attachment: pgpEWw7hQLKxl.pgp
Description: PGP signature


--- End Message ---

Reply via email to