Your message dated Tue, 08 Oct 2019 23:49:11 +0000
with message-id <e1ihze7-0004kj...@fasolo.debian.org>
and subject line Bug#925628: fixed in afnix 2.9.2-2
has caused the Debian Bug report #925628,
regarding afnix: ftbfs with GCC-9
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.)


-- 
925628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:afnix
Version: 2.9.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/afnix_2.9.2-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 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-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
make[6]: Entering directory '/<<PKGBUILDDIR>>/prj/std/sps/src'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/prj/std/sps/src'
make[5]: Leaving directory '/<<PKGBUILDDIR>>/prj/std/sps'
make[5]: Entering directory '/<<PKGBUILDDIR>>/prj/std/tls'
make[6]: Entering directory '/<<PKGBUILDDIR>>/prj/std/tls/src'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/prj/std/tls/src'
make[5]: Leaving directory '/<<PKGBUILDDIR>>/prj/std/tls'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/prj/std'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/prj'
make[3]: Entering directory '/<<PKGBUILDDIR>>/tst'
make[4]: Entering directory '/<<PKGBUILDDIR>>/tst/ref'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tst/ref'
make[4]: Entering directory '/<<PKGBUILDDIR>>/tst/mod'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tst/mod'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/tst'
make[3]: Entering directory '/<<PKGBUILDDIR>>/exp'
make[4]: Entering directory '/<<PKGBUILDDIR>>/exp/ref'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/exp/ref'
make[4]: Entering directory '/<<PKGBUILDDIR>>/exp/api'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/exp/api'
make[4]: Entering directory '/<<PKGBUILDDIR>>/exp/prj'
make[5]: Entering directory '/<<PKGBUILDDIR>>/exp/prj/amd'
make[6]: Entering directory '/<<PKGBUILDDIR>>/exp/prj/amd/src'
make[7]: Entering directory '/<<PKGBUILDDIR>>/exp/prj/amd/src/app'
make[7]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj/amd/src/app'
make[7]: Entering directory '/<<PKGBUILDDIR>>/exp/prj/amd/src/tst'
make[7]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj/amd/src/tst'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj/amd/src'
make[6]: Entering directory '/<<PKGBUILDDIR>>/exp/prj/amd/doc'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj/amd/doc'
make[5]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj/amd'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/exp/prj'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/exp'
make[3]: Entering directory '/<<PKGBUILDDIR>>/doc'
make[4]: Entering directory '/<<PKGBUILDDIR>>/doc/dtd'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/doc/dtd'
make[4]: Entering directory '/<<PKGBUILDDIR>>/doc/etc'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/doc/etc'
make[4]: Entering directory '/<<PKGBUILDDIR>>/doc/xml'
make[5]: Entering directory '/<<PKGBUILDDIR>>/doc/xml/eul'
make[5]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml/eul'
make[5]: Entering directory '/<<PKGBUILDDIR>>/doc/xml/vol'
make[6]: Entering directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-0'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-0'
make[6]: Entering directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-1'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-1'
make[6]: Entering directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-2'
make[6]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml/vol/vol-2'
make[5]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml/vol'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/doc/xml'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/doc'
make[3]: Entering directory '/<<PKGBUILDDIR>>/etc'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/etc'
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
rm -rf bld
dh_clean
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_clean
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
./cnf/bin/afnix-setup -o --prefix=/usr
afnix-setup: cannot find compiler file error: cannot find version for compiler 
gcc
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:11: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

--- End Message ---
--- Begin Message ---
Source: afnix
Source-Version: 2.9.2-2

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu <iwama...@debian.org> (supplier of updated afnix 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: SHA256

Format: 1.8
Date: Wed, 09 Oct 2019 08:28:05 +0900
Source: afnix
Architecture: source
Version: 2.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu <iwama...@debian.org>
Changed-By: Nobuhiro Iwamatsu <iwama...@debian.org>
Closes: 925628
Changes:
 afnix (2.9.2-2) unstable; urgency=medium
 .
   * Fix build with gcc-9 (Closes: #925628)
     - Add d/patches/use-dpkg-buildflags-for-gcc9.patch.
     - Add d/patches/Add-support-gcc9.patch.
Checksums-Sha1:
 42673b1bbdd426d3a872e0a56dce22dea57854b5 1887 afnix_2.9.2-2.dsc
 17daa61076426bf9e9f5c1a2662b641ff97559e9 8980 afnix_2.9.2-2.debian.tar.xz
 ce8140795c7d51b7fb70c413b261eaf366182027 5887 afnix_2.9.2-2_amd64.buildinfo
Checksums-Sha256:
 2ced962c9b8f1c19bf49389a1094818fde0f57445e7e70ec9e1e93d95353fe0a 1887 
afnix_2.9.2-2.dsc
 3cd529580c0158620a042ee4ae519dd706a8b2c4f709790a9ae23f9279c011ab 8980 
afnix_2.9.2-2.debian.tar.xz
 b7495d1c0a1328a2264b46a34332d50ebb63d8e269b197e51318a6d8bba60087 5887 
afnix_2.9.2-2_amd64.buildinfo
Files:
 7667fa789c60e9523aeca08d656abe49 1887 interpreters optional afnix_2.9.2-2.dsc
 638aa82bd5b5e59e69402eb5ba4a6ca7 8980 interpreters optional 
afnix_2.9.2-2.debian.tar.xz
 0af4c9d846cf975848a100a775562df0 5887 interpreters optional 
afnix_2.9.2-2_amd64.buildinfo

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

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAl2dHRUACgkQMiR/u0Ct
H6YloBAAlTsGeZkS7cFHRzNOGhtgp/ICCcrbP/9pl4ILPjI5/2UPU9zqvJcD3f61
A/4RLMPn4viu3krTWsUOBtWyqkZScB4dDwyfKf/M0q+F7WPdXDF9F8E7ZU/J7xWT
fyK236Pqnp+L7lt0bo2sGNpAiYh4xd57UQq/AWzgFJYoUwDTpi3s5WX9hsz/duW2
pZuVrKyEweiAcwYF4/dgjjCN08waDXFtdXwuhFokpttEb285HNIj/ODA7HChE1/k
RbIJuU7qq1GhR3GvP8/ENP/21CAqt+KHFduIekHr+mclL4Eu5MudhEkjJL0A8Xpf
1PnK0aV34SJ2jYWKsQ5HGNGsSyCW+kCxvmAkXaHzSlXAKPc2jcO/DLyoTfvc12yD
TGLGtV2b5gFcw3r8JZzWUKu6R4lt3ocCqhlBPs3GFmazYeH4MJBRG82vPYbVkZyi
cpPFKNGQkXmGQRjH2HwC1ZLQ0+yu4WUune4yAUCw1C5IZ/OUJ5E63UFc9JAoTuoH
9Tr+m40P4JwV3JXeWEmpHRFM4SGTJ4qZOYzXAlc/O3f47lPF1HtBwP2/28/31r/8
u5Y/9zAiqovAlrLoDOGvfxKFjUaOavzJdklTi67z6E1mmIfgvBw7+XmVOAED+NoU
ivimWWam3J/x5MIXEuexmPfNDJ/39tgId9rHPA06JnaicMpdiaw=
=+OBA
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to