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

Bug#1074850: marked as done (bmf: ftbfs with GCC-14)

Your message dated Fri, 28 Mar 2025 14:34:35 +0000
with message-id <E1tyAn5-0018YA-7T@fasolo.debian.org>
and subject line Bug#1074850: fixed in bmf 0.9.4-14
has caused the Debian Bug report #1074850,
regarding bmf: 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 owner@bugs.debian.org
immediately.)


-- 
1074850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074850
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:bmf
Version: 0.9.4-13
Severity: important
Tags: sid trixie
User: debian-gcc@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/bmf_0.9.4-13_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

[...]
make[2]: Entering directory '/<<PKGBUILDDIR>>'
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -DPACKAGE=\"bmf\" -DVERSION=\"0.9.4\" -c bmf.c
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o filt.o filt.c
filt.c: In function ‘statdump’:
filt.c:42:17: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
   42 |                 write( fd, iobuf, p-iobuf );
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
filt.c:49:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
   49 |         write( fd, iobuf, p-iobuf );
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbmysql.o dbmysql.c
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbdb.o dbdb.c
dbdb.c: In function ‘dbdb_table_export’:
dbdb.c:588:17: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  588 |                 write( fd, iobuf, p-iobuf );
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~
dbdb.c:597:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  597 |         write( fd, iobuf, p-iobuf );
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbtext.o dbtext.c
dbtext.c: In function ‘dbtext_table_mergeclose’:
dbtext.c:329:5: warning: ignoring return value of ‘ftruncate’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  329 |     ftruncate( pthis->fd, 0 );
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
dbtext.c:399:13: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  399 |             write( pthis->fd, iobuf, p-iobuf );
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dbtext.c:405:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  405 |         write( pthis->fd, iobuf, p-iobuf );
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dbtext.c: In function ‘dbtext_table_unmergeclose’:
dbtext.c:428:5: warning: ignoring return value of ‘ftruncate’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  428 |     ftruncate( pthis->fd, 0 );
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
dbtext.c:499:13: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  499 |             write( pthis->fd, iobuf, p-iobuf );
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dbtext.c:505:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  505 |         write( pthis->fd, iobuf, p-iobuf );
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbh.o dbh.c
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -pedantic -DNDEBUG -D_UNIX -D_LINUX -Wall -DHAVE_LIBDB -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -c -o lex.o lex.c
lex.c: In function ‘is_base64char’:
lex.c:189:22: error: type of ‘c’ defaults to ‘int’ [-Wimplicit-int]
  189 | static inline bool_t is_base64char(c)
      |                      ^~~~~~~~~~~~~
lex.c: In function ‘is_wordmidchar’:
lex.c:194:22: error: type of ‘c’ defaults to ‘int’ [-Wimplicit-int]
  194 | static inline bool_t is_wordmidchar(c)
      |                      ^~~~~~~~~~~~~~
lex.c: In function ‘is_wordendchar’:
lex.c:199:22: error: type of ‘c’ defaults to ‘int’ [-Wimplicit-int]
  199 | static inline bool_t is_wordendchar(c)
      |                      ^~~~~~~~~~~~~~
lex.c: In function ‘lex_passthru’:
lex.c:731:13: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  731 |             write( STDOUT_FILENO, pbuf, len );
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
lex.c:739:5: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  739 |     write( STDOUT_FILENO, szbuf, strlen(szbuf) );
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
lex.c:744:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  744 |         write( STDOUT_FILENO, pthis->pbuf+pthis->pos, pthis->eom-pthis->pos );
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [<builtin>: lex.o] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:16: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: bmf
Source-Version: 0.9.4-14
Done: David da Silva Polverari <polverari@debian.org>

We believe that the bug you reported is fixed in the latest version of
bmf, 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 1074850@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David da Silva Polverari <polverari@debian.org> (supplier of updated bmf 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: SHA256

Format: 1.8
Date: Fri, 28 Mar 2025 13:27:31 +0000
Source: bmf
Architecture: source
Version: 0.9.4-14
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: David da Silva Polverari <polverari@debian.org>
Closes: 1074850
Changes:
 bmf (0.9.4-14) unstable; urgency=medium
 .
   * QA upload.
   * debian/control: bumped Standards-Version to 4.7.2.
   * debian/copyright: updated packaging copyright information.
   * debian/patches/50-fix-ftbfs-gcc-14.patch: added to fix FTBFS on GCC 14.
     (Closes: #1074850)
   * debian/rules: removed unnecessary lines.
   * debian/watch: bumped to version 4.
Checksums-Sha1:
 ab0319d54c95893ea24ac8442c74f0c21dbbeec6 1818 bmf_0.9.4-14.dsc
 6cd9cdcc514e03b9820efe2661bfd8bdc6fafdb2 6664 bmf_0.9.4-14.debian.tar.xz
 f8d35c68e951342e6b12b4f7fd7bbf83e915fc9a 5440 bmf_0.9.4-14_source.buildinfo
Checksums-Sha256:
 3f055b8e91f79122919ae239a91075adf518153d0cd15c9b6f182010b5e0e04a 1818 bmf_0.9.4-14.dsc
 edcf6052b5877703c092c9c03409d34201d664bd128f3b0e0c9dfdc1c88f1acd 6664 bmf_0.9.4-14.debian.tar.xz
 4785e05069bba87d9aa84c5e7f8ebad61170ac6360b86b86c500f127f3ffcb42 5440 bmf_0.9.4-14_source.buildinfo
Files:
 b3414d1fc461d51331122c1c78d6e4ae 1818 mail optional bmf_0.9.4-14.dsc
 b8442c44866c4b37424965855342d4b3 6664 mail optional bmf_0.9.4-14.debian.tar.xz
 755e0c4e55c9f127f64f766f3d855bcd 5440 mail optional bmf_0.9.4-14_source.buildinfo

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

iQIzBAEBCAAdFiEEDTUunGhzKyZWj9leHIjoaIRpgN4FAmfmryMACgkQHIjoaIRp
gN435xAAwyxno26CBn+UmTa79/QF7fFzMBgUq7eAqmaRQdKhtYUy2x4RxkZadzeq
rgM6gwBb60Wwevi8HFzcitJa4/UkW4KMocLF1YnMHEFqkita+9SjHrel9pcrnlEo
3FPAv6KP+w2cbJ+scd2n8eBDle+YYUyOSSJqj4vvljCn/l8W2+M/m3lsuGiJL1eh
sfZxdCTVz9Xv1gL18CnmQ7YO3f6ZXFytCmD4EOoT2BMfbFIexzgdRvxrLc1RnhW8
/slsMK4IjBho24GnyyNv+RjQnAnHj0Ii7YtHNQscwOq0gEq6ybeSA0YN2HIDy/v8
7vTLcB3CaV9VcIrnqlPrK1JWyY1xmSv6IOfRTSUPUmHkq9vJy8LmrcFBmylKsoa6
Hm2OSnOOTbHTsnPDxFEaAt3V4fydGjJndPJV1q4fS0vhm4zuPihTXOFe/sMATNmC
pSZUCuOWxy77J/3Wg0MsobRo087tgUMo5ZlV8hH62rvNcw1SYhi5nMp7ec0E058P
QwIGa6pbPn4T61ERJvJbAZPpJnj7Bkut8SyVhUTAesNA2EaiQF692cgMneZhW+vc
9iqrbiMB9xvYuEN24QvNL0ZvYuf05xMHHYghtxs2/T2SNppKoTzDsK+7lArIGWEn
z5nJy16JJS/U7FzuN2ThUe52FmlC7WiD2Uy8loTeKHzPh2+ZrQM=
=bwXG
-----END PGP SIGNATURE-----

Attachment: pgpLPdau5TdBm.pgp
Description: PGP signature


--- End Message ---
Reply to: