In file included from /var/tmp/portage/media-plugins/gst-plugins-neon-1.14.5/work/gst-plugins-bad-1.14.5/ext/neon/gstneonhttpsrc.c:21: /var/tmp/portage/media-plugins/gst-plugins-neon-1.14.5/work/gst-plugins-bad-1.14.5/ext/neon/gstneonhttpsrc.h:26:10: fatal error: ne_session.h: No such file or directory 26 | #include <ne_session.h> | ^~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-20200404-094844 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.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.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.42.0 * The following VMs are available for generation-2: *) IcedTea JDK 3.15.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 of HEAD at this tinderbox image: /var/db/repos/gentoo Thu 09 Apr 2020 07:37:54 AM UTC emerge -qpvO media-plugins/gst-plugins-neon [ebuild N ] media-plugins/gst-plugins-neon-1.14.5 ABI_X86="(64) -32 (-x32)"
Created attachment 631570 [details] emerge-info.txt
Created attachment 631572 [details] emerge-history.txt
Created attachment 631574 [details] environment
Created attachment 631576 [details] etc.portage.tbz2
Created attachment 631578 [details] logs.tbz2
Created attachment 631580 [details] media-plugins:gst-plugins-neon-1.14.5:20200409-081341.log
Created attachment 631582 [details] temp.tbz2
The problem is that the configure script rejects neon 0.31 and later, so if an up-to-date version is installed this simply won't build. I don't think there's any reason to do this; according to the changelog 0.31 is fully ABI and API compatible with the previous version. gst-plugins-neon-1.16.2 has the same issue so you're probably going to get more people complaining about this as they upgrade. It looks like even that newer version predates neon 0.31 which may explain things.
Still happens for gst-plugins-neon-1.16.2 when neon-0.31.2 is installed.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=613b047b7b3b5c4ffcb22bc3fa433f11ef0725c5 commit 613b047b7b3b5c4ffcb22bc3fa433f11ef0725c5 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2021-02-13 21:53:41 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2021-02-13 21:53:41 +0000 media-plugins/gst-plugins-neon: fix build with neon-0.31 Closes: https://bugs.gentoo.org/716786 Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Mart Raudsepp <leio@gentoo.org> media-plugins/gst-plugins-neon/gst-plugins-neon-1.16.3.ebuild | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
