c++ -O2 -pipe -march=native -Wall -Wextra -Werror -I../include -fpic -D_FILE_OFFSET_BITS=64 -std=c++11 -Wold-style-cast -fPIC -o crc64.o -c crc64.cc c++ -O2 -pipe -march=native -Wall -Wextra -Werror -I../include -fpic -D_FILE_OFFSET_BITS=64 -std=c++11 -Wold-style-cast -fPIC -o error.o -c error.cc error.cc:35:54: error: non-local lambda expression cannot have a capture-default 35 | function<void(string s)> current_catch_explainer = [&](string s) { | ^ make[1]: *** [Makefile:43: error.o] Error 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_20190510-222116 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.34.1 * emerge -qpvO sys-fs/bees [ebuild N ] sys-fs/bees-0.6 USE="-tools"
Created attachment 576156 [details] emerge-info.txt
Created attachment 576158 [details] emerge-history.txt
Created attachment 576160 [details] environment
Created attachment 576162 [details] etc.portage.tbz2
Created attachment 576164 [details] sys-fs:bees-0.6:20190512-114013.log
Created attachment 576166 [details] temp.tbz2
Does it also occur with the 9999 ebuild?
Yes, it also happens with the -9999 ebuild. It only happens with GCC 9.1 though (in either case). It builds fine with GCC 8.3. I have not tried clang or other GCC versions.
I've seen it's already reported upstream: https://github.com/Zygo/bees/issues/112
It's now been fixed upstream and this patch can be applied: https://github.com/Zygo/bees/commit/228747a8f8925fd11ed1462a4140decdb7afaedb.patch
Zygo wrote it will be fixed in v0.7, I'm bumping the version in portage as soon as the version is tagged. I'll link this bug to the Portage PR then.
Bugfix release v0.6.2 is going to be tagged and I'll bump the ebuild.
I've added a hotfix because of slow upstream...
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2a8f934671d15ac008f42976e5c4de087e31607 commit b2a8f934671d15ac008f42976e5c4de087e31607 Author: Kai Krakow <hurikhan77+bgo@gmail.com> AuthorDate: 2019-11-28 11:23:02 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2019-11-28 16:34:35 +0000 sys-fs/bees: Bump to v0.6.1-r1 Closes: https://bugs.gentoo.org/685714 Package-Manager: Portage-2.3.76, Repoman-2.3.16 Signed-off-by: Kai Krakow <hurikhan77+bgo@gmail.com> Signed-off-by: Joonas Niilola <juippis@gentoo.org> sys-fs/bees/bees-0.6.1-r1.ebuild | 86 ++++++++++++++++++++ ...-local-lambda-expression-cannot-have-a-ca.patch | 38 +++++++++ ...karound-to-prevent-LOGICAL_INO-and-btrfs-.patch | 95 ++++++++++++++++++++++ 3 files changed, 219 insertions(+)
