[Douglas Mencken] > checking neon library version... 0.29.6 > configure: error: cannot find Neon > ERROR: './configure' error. Abort. > > Al least, "cannot find Neon" is an absolutely WRONG message. Some > autoconf stuff needs to be fixed. > > From config.log: > > configure:4944: checking neon library > configure:5401: checking neon library version > configure:5408: result: 0.29.6 > configure:5456: powerpc-gnu-linux-uclibc-gcc -o conftest -g -O2 -g > -O2 -pthread -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/neon > -D > _REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE conftest.c -lneon >&5 > /tmp/cckaQroR.o: In function `main': > /root/build-farm/svn-v1.6.17.builddir/conftest.c:16: undefined > reference to `ne_xml_create' > collect2: ld returned 1 exit status
Thanks, clarified in r1153599 to read "Cannot find a usable Neon library". That's what we test: try to use a neon function we need, try to link to the neon library. If there's a link error, it might be because the library isn't usable by anyone, or it might be because it doesn't have the function we need. It isn't easy to tell the difference, actually, given the range of compilers and linkers and human languages in which they might report these errors. Anyway, the semantic difference between "Cannot find neon library" and "Cannot find neon library that will work for us" is pretty small. (It's news to me, in fact, that it was even possible to build a recent version of neon in such a way that it doesn't support the features we use.) -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
