Summary: | app-backup/bareos-19.2.9 - /.../sd_reservation.cc: error: sleep_for is not a member of std::this_thread (maybe gcc-11 related) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Marc Schiffbauer <mschiff> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kfm, sam, treecleaner |
Priority: | Normal | Keywords: | UPSTREAM |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.bareos.org/view.php?id=1388 | ||
Whiteboard: | ~arch only, fixed by 19.2.11? | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 732706 | ||
Attachments: |
emerge-info.txt
app-backup:bareos-19.2.9:20210429-100941.log emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2021-04-29 12:12:54 UTC
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(+) ping 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 |