Your message dated Thu, 4 Aug 2022 00:51:25 +0200
with message-id 
<CAKNHny87mm2jJcAWBpTVZ5pPHX=xvavwtydi7sh6buyrycu...@mail.gmail.com>
and subject line Re: dustmite: ftbfs with GCC-12
has caused the Debian Bug report #1012915,
regarding dustmite: ftbfs with GCC-12
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.)


-- 
1012915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dustmite
Version: 0~20170126.e95dff8-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/dustmite_0~20170126.e95dff8-3_unstable_gcc12.log
The last lines of the build log are at the end of this report.

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

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-d2d85b1e-aa13-484d-a849-21572e94a7e3
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-----------------

Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package dustmite
dpkg-buildpackage: info: source version 0~20170126.e95dff8-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Matthias Klumpp <m...@debian.org>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   debian/rules override_dh_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f dustmite
dh_clean
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
gdc -odustmite \
        -g -O2 -fstack-protector-strong \
        -Wl,-z,relro \
        -Wall \
        dustmite.d splitter.d
dustmite.d:41:26: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                          ^
dustmite.d:41:33: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                 ^
dustmite.d:41:39: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                       ^
dustmite.d:41:49: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                 ^
dustmite.d:41:61: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                             ^
dustmite.d:41:67: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                                   ^
dustmite.d:41:74: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                                         
 ^
dustmite.d:41:85: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                                         
            ^
dustmite.d:41:98: error: undefined identifier ‘StopWatch’
   41 | struct Times { StopWatch total, load, testSave, resultSave, test, 
clean, cacheHash, globalCache, misc; }
      |                                                                         
                         ^
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Control: fixed 1012915 0.0.430-1

Hi!
I can't reproduce this at all when trying to build the latest version
locally, so I guess this must have already been resolved with the
latest version (which unfortunately was uploaded pretty much around
the same time when this bug was filed).
Please feel free to reopen or file a new bug in case this isn't fixed :-)

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

--- End Message ---

Reply via email to