To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'MSCGEN_PATH' at line 2030 of file 'reference.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" /var/tmp/portage/media-libs/liblo-0.31/work/liblo-0.31/lo/lo_cpp.h:128: warning: include file cassert not found, perhaps you forgot to add its directory to INCLUDE_PATH? make[2]: *** [Makefile:471: doxygen-build.stamp] Segmentation fault make[2]: Leaving directory '/var/tmp/portage/media-libs/liblo-0.31/work/liblo-0.31/doc' make[1]: *** [Makefile:471: all-recursive] Error 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-j4-20211217-040058 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-11.2.1 * clang version 13.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.9 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.57.0 * php cli: [1] php7.3 [2] php7.4 [3] php8.1 * HEAD of ::gentoo commit c4203d93a6ff7115fdc1b4d7a7525122aff8edd8 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Dec 18 00:51:44 2021 +0000 2021-12-18 00:51:43 UTC emerge -qpvO media-libs/liblo [ebuild N ] media-libs/liblo-0.31 USE="ipv6 -doc -static-libs"
Created attachment 759543 [details] emerge-info.txt
Created attachment 759544 [details] emerge-history.txt
Created attachment 759545 [details] environment
Created attachment 759546 [details] etc.portage.tar.bz2
Created attachment 759547 [details] logs.tar.bz2
Created attachment 759548 [details] media-libs:liblo-0.31:20211218-023457.log
Created attachment 759549 [details] temp.tar.bz2
is 0.32 affected?
I bet this is a dupe of bug 912986. *** This bug has been marked as a duplicate of bug 912986 ***
(In reply to Miroslav Šulc from comment #8) > is 0.32 affected? no