checking linking against neon... no configure: incompatible neon library version 0.30.2: wanted 0.27 28 29 30 configure: error: could not find neon !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-fs/davfs2-1.5.4/work/davfs2-1.5.4/config.log ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-no-multilib-libressl-unstable_20170122-225602) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) java-config: The following VMs are available for generation-2: -----------------------------------------------------------------
Created attachment 462052 [details] emerge-info.txt
Created attachment 462054 [details] config.log
Created attachment 462056 [details] emerge-history.txt
Created attachment 462058 [details] environment
Created attachment 462060 [details] etc.portage.tbz2
Created attachment 462062 [details] net-fs:davfs2-1.5.4:20170131-235320.log
I can't immediately reproduce this: Configuration for building davfs2 1.5.4: Install Prefix: /usr Compiler: x86_64-pc-linux-gnu-gcc Large File Support: no Neon Library: library in /usr (0.30.2) SSL is supported by neon National Language Support: libc
(In reply to Göktürk Yüksek from comment #7) maybe related to neon-0.30.2 (/usr/lib64/libneon.so.27.3.2) b/c 0.30.1 (/usr/lib64/libneon.so.27.3.1) seems to work here.
It does configure with 0.30.2 for me as comment 7 shows. Maybe an autotools thing, will look at it deeper later on.
Bug 719954 had a similar issue which I fixed for 1.5.6. I cannot reproduce this one. I'll take another look if your tinderbox catches anything like this for 1.5.6-r1.