/var/tmp/portage/app-backup/bareos-19.2.9/work/bareos-Release-19.2.9/core/src/tests/sd_reservation.cc: In function ‘void WaitThenUnreserve(std::unique_ptr<TestJob>&)’: /var/tmp/portage/app-backup/bareos-19.2.9/work/bareos-Release-19.2.9/core/src/tests/sd_reservation.cc:147:21: error: ‘sleep_for’ is not a member of ‘std::this_thread’ 147 | std::this_thread::sleep_for(std::chrono::milliseconds(10)); | ^~~~~~~~~ ninja: build stopped: subcommand failed. * ERROR: app-backup/bareos-19.2.9::gentoo failed (compile phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-20210415-101632 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.1 [3] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.8.9 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.51.0 * The following VMs are available for generation-2: 1) IcedTea JDK 3.18.0 [icedtea-8] 2) JamVM JDK 2.0.0 [jamvm] *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] jamvm [3] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Apr 28 23:50:13 UTC 2021 emerge -qpvO app-backup/bareos [ebuild N ] app-backup/bareos-19.2.9 USE="X acl director ipv6 postgres readline storage-daemon tcpd xattr -ceph -clientonly -glusterfs -jansson (-libressl) -lmdb -logwatch -mysql -ndmp -scsi-crypto -sqlite -static -systemd -vim-syntax"
Created attachment 703812 [details] emerge-info.txt
Created attachment 703815 [details] app-backup:bareos-19.2.9:20210429-100941.log
Created attachment 703818 [details] emerge-history.txt
Created attachment 703821 [details] environment
Created attachment 703824 [details] etc.portage.tar.bz2
Created attachment 703827 [details] logs.tar.bz2
Created attachment 703830 [details] temp.tar.bz2
ping
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0f65fc8909308003cdfe8d933b06b5a054c7715e commit 0f65fc8909308003cdfe8d933b06b5a054c7715e Author: David Seifert <soap@gentoo.org> AuthorDate: 2021-08-05 08:21:27 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2021-08-05 08:21:27 +0000 profiles: last-rite app-backup/bareos Bug: https://bugs.gentoo.org/631598 Bug: https://bugs.gentoo.org/690024 Bug: https://bugs.gentoo.org/735960 Bug: https://bugs.gentoo.org/749038 Bug: https://bugs.gentoo.org/761415 Bug: https://bugs.gentoo.org/761667 Bug: https://bugs.gentoo.org/778557 Bug: https://bugs.gentoo.org/786789 Bug: https://bugs.gentoo.org/799179 Signed-off-by: David Seifert <soap@gentoo.org> profiles/package.mask | 8 ++++++++ 1 file changed, 8 insertions(+)
This is addressed by the release of 19.2.11. See https://github.com/bareos/bareos/commit/7a7cb96. Incidentally, 18.2.10 does not compile because, among other things, it triggers several compiler warnings that are treated as errors. These include "class-memaccess", "unused-variable", "address" and "unused-function". Indeed, I don't see how it could possibly have been able to compile since the release of GCC 8.0, at the very least. Given that the 18.x series is obsolete, I would suggest getting rid of it.
Sorry, I meant to say that the issue of the missing <thread> header was addressed by 19.2.10 (not 19.2.11). However, both 19.2.10 and 19.2.11 fail to build for distinct reasons. In short, this bug is OBSOLETE and a new one is required.
This bug predates dev-libs/boost-1.77.0 version bump.
(In reply to Kerin Millar from comment #11) > This is addressed by the release of 19.2.11. See > https://github.com/bareos/bareos/commit/7a7cb96. > > Incidentally, 18.2.10 does not compile because, among other things, it > triggers several compiler warnings that are treated as errors. These include > "class-memaccess", "unused-variable", "address" and "unused-function". > Indeed, I don't see how it could possibly have been able to compile since > the release of GCC 8.0, at the very least. Given that the 18.x series is > obsolete, I would suggest getting rid of it. As far as I can tell, 18.2 is still being maintained. 18.2.12 had been released in september. For me all bareos versions in tree compile with gcc-11. Are you OK with closing this bug?
(In reply to Marc Schiffbauer from comment #14) > (In reply to Kerin Millar from comment #11) > > This is addressed by the release of 19.2.11. See > > https://github.com/bareos/bareos/commit/7a7cb96. > > > > Incidentally, 18.2.10 does not compile because, among other things, it > > triggers several compiler warnings that are treated as errors. These include > > "class-memaccess", "unused-variable", "address" and "unused-function". > > Indeed, I don't see how it could possibly have been able to compile since > > the release of GCC 8.0, at the very least. Given that the 18.x series is > > obsolete, I would suggest getting rid of it. > > As far as I can tell, 18.2 is still being maintained. 18.2.12 had been > released in september. I see. Curiously, it still doesn't compile here. > > For me all bareos versions in tree compile with gcc-11. > > Are you OK with closing this bug? Yes, thanks. I'll look into the issue with 18.2.12 further and file a distinct bug if necessary.
Closing as this specific issue seems to be fixed
