c++ lv2.cpp /var/tmp/portage/media-libs/lsp-plugins-1.1.10/work/lsp-plugins-lsp-plugins-1.1.10/include/metadata/modules.h: In function void* lsp::lv2_instantiate(const lsp::_LV2_Descriptor*, double, const char*, const LV2_Feature* const*): lv2.cpp:84:82: error: invalid use of incomplete type const struct lsp::_LV2_Descriptor 84 | && (plugin::metadata.lv2_uid != NULL) && (!strcmp(descriptor->URI, LSP_PLUGIN_URI(lv2, plugin)))) \ | ^~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-libressl-20200611-183812 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.1 [2] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.44.0 * The following VMs are available for generation-2: *) IcedTea JDK 3.16.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon 15 Jun 2020 03:05:45 PM UTC /var/db/repos/libressl Sun 14 Jun 2020 10:05:23 PM UTC emerge -qpvO media-libs/lsp-plugins [ebuild N ] media-libs/lsp-plugins-1.1.10 USE="lv2 -doc -jack -ladspa"
Created attachment 644872 [details] emerge-info.txt
Created attachment 644874 [details] emerge-history.txt
Created attachment 644876 [details] environment
Created attachment 644878 [details] etc.portage.tbz2
Created attachment 644880 [details] media-libs:lsp-plugins-1.1.10:20200615-154858.log
Created attachment 644882 [details] temp.tbz2
I wonder if git master has a fix, can you verify? Is this a gcc10 bug (I just tested with gcc-9).
1.1.22 is also now available to test
Seen a user run into this (using gcc9) which they solved by using 1.1.24 instead of stable 1.1.7-r1, maybe it's due time to just stabilize that one? I believe related to newer media-libs/lv2 but there's only one version (1.18.0) of it in tree now. Upstream changelogs since 1.1.22: >Fixed build broken by recent LV2 header updates. So I assume any earlier versions are broken with USE=lv2 right now.
amd64 done
x86 done all arches done
