/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: brightonCLI.o:(.bss+0x0): multiple definition of `event'; brightonMixerMenu.o:(.bss+0x0): first defined here collect2: error: ld returned 1 exit status ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-20201109-205253 ------------------------------------------------------------------- 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-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) [5] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-1.47.0 * The following VMs are available for generation-2: 1) IcedTea JDK 3.17.0 [icedtea-8] 2) JamVM JDK 2.0.0 [jamvm] *) AdoptOpenJDK 8.272_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.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sat Nov 21 01:07:15 AM UTC 2020 emerge -qpvO media-sound/bristol [ebuild N ] media-sound/bristol-0.60.11-r1 USE="alsa -oss -static-libs"
this seems to be either still an issue or a similarity to the one reported in bug 708046
Created attachment 673996 [details] emerge-info.txt
Created attachment 673999 [details] emerge-history.txt
Created attachment 674002 [details] environment
Created attachment 674005 [details] etc.portage.tbz2
Created attachment 674008 [details] logs.tbz2
Created attachment 674011 [details] media-sound:bristol-0.60.11-r1:20201121-060352.log
Created attachment 674014 [details] temp.tbz2
*** This bug has been marked as a duplicate of bug 746347 ***