from application.cpp:27: ../../type_safe/include/type_safe/constrained_type.hpp: In lambda function: ../../type_safe/external/debug_assert/debug_assert.hpp:364:72: error: expected ‘{’ before ‘noexcept’ 364 | DEBUG_ASSERT_PURE_FUNCTION noexcept { return Expr; }, \ | ^~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_libressl_20190510-223704 ------------------------------------------------------------------- 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) [3] jython2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-bin-1.34.2 [2] rust-1.34.2 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO sci-electronics/librepcb [ebuild N ] sci-electronics/librepcb-0.1.0
Created attachment 577192 [details] emerge-info.txt
Created attachment 577194 [details] emerge-history.txt
Created attachment 577196 [details] environment
Created attachment 577198 [details] etc.portage.tbz2
Created attachment 577200 [details] sci-electronics:librepcb-0.1.0:20190518-151648.log
Created attachment 577202 [details] temp.tbz2
There is a hacky workaround though. I am using a mac as my pc doesn't function, so I can't help here. https://github.com/foonathan/debug_assert/issues/17#issuecomment-495928357
(In reply to Petross404(Petros S) from comment #7) > There is a hacky workaround though. I am using a mac as my pc doesn't > function, so I can't help here. > > https://github.com/foonathan/debug_assert/issues/17#issuecomment-495928357 The same thread includes a slightly better suggestion that the -DDEBUG_ASSERT_PURE= workaround, by using [[gnu:pure]] in the macro instead. Here is the patch that I've put into my /etc/portage/patches
Created attachment 588622 [details, diff] Patch for failing DEBUG_ASSERT_PURE_FUNCTION macro Workaround patch for the failure with the DEBUG_ASSER_PURE_FUNCTION macro under GCC 9
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0157dea7d399b863d1f9d5f201e0915d8e1b4f15 commit 0157dea7d399b863d1f9d5f201e0915d8e1b4f15 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-05-21 18:29:42 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-05-21 18:29:42 +0000 sci-electronics/librepcb: Drop 0.1.0-r1 Closes: https://bugs.gentoo.org/686228 Closes: https://bugs.gentoo.org/694648 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> sci-electronics/librepcb/Manifest | 1 - sci-electronics/librepcb/librepcb-0.1.0-r1.ebuild | 36 ----------------------- 2 files changed, 37 deletions(-)
