You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Douglas Mencken <do...@gmail.com> on 2011/08/03 19:11:56 UTC
[build error] configure error when using libneon build with no xml support
It prints:
checking for APR... yes
checking APR version... 1.4.5
configure: Apache Portable Runtime Utility (APRUTIL) library configuration
checking for APR-util... yes
checking APR-UTIL version... 1.3.12
checking for pkg-config... /usr/bin/pkg-config
configure: checking neon library
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
configure:5456: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "subversion"
| #define PACKAGE_TARNAME "subversion"
| #define PACKAGE_VERSION "1.6.17"
| #define PACKAGE_STRING "subversion 1.6.17"
| #define PACKAGE_BUGREPORT "http://subversion.tigris.org/"
| #define PACKAGE_URL ""
| #define SVN_NEON_0_26 1
| #define SVN_NEON_0_27 1
| #define SVN_NEON_0_28 1
| /* end confdefs.h. */
|
| #include <ne_compress.h>
| #include <ne_xml.h>
| int main()
| {ne_xml_create(); ne_decompress_destroy(NULL);}
configure:5470: 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 -lintl -lz -lssl -lcrypto -ldl -lneon >&5
/tmp/ccL895Xt.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
configure:5470: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "subversion"
| #define PACKAGE_TARNAME "subversion"
Re: [build error] configure error when using libneon build with no
xml support
Posted by Rainer Jung <ra...@kippdata.de>.
On 04.08.2011 11:07, Julian Foad wrote:
> Peter Samuelson wrote:
>> [Peter Samuelson]
>>> (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.)
>>
>> Followup from IRC: we determined that the reason Doug's neon library
>> didn't support XML functions is, he used 'configure --without-webdav'.
>> If you don't say --without-webdav, the neon configure script will
>> indeed find an appropriate XML library or die trying.
>>
>> Now ... it would be possible to detect, explicitly, that neon was built
>> --without-webdav, and tailor our error appropriately. But it'd be ugly
>> code. Is it worth it? Do other users run into this problem?
>
> I'd say, don't look for this specific problem, just change our error
> message to be more honest. 'configure' has already printed
>
> "checking neon library version... 0.29.6"
>
> and the problem with the current error message
>
> "cannot find Neon"
>
> was simply that it contradicts the earlier message. So, on failure to
> compile and link a test program, just make the message say something
> like
>
> "failed to compile and link a test program"
>
> instead. That's enough to make the user look at 'config.log' for more
> details.
<bikeshed>
checking neon usability... no
</bikeshed>
This is similar to the standard header checks, e.g.
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
Regards,
Rainer
Re: [build error] configure error when using libneon build with no
xml support
Posted by Julian Foad <ju...@wandisco.com>.
Peter Samuelson wrote:
> [Peter Samuelson]
> > (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.)
>
> Followup from IRC: we determined that the reason Doug's neon library
> didn't support XML functions is, he used 'configure --without-webdav'.
> If you don't say --without-webdav, the neon configure script will
> indeed find an appropriate XML library or die trying.
>
> Now ... it would be possible to detect, explicitly, that neon was built
> --without-webdav, and tailor our error appropriately. But it'd be ugly
> code. Is it worth it? Do other users run into this problem?
I'd say, don't look for this specific problem, just change our error
message to be more honest. 'configure' has already printed
"checking neon library version... 0.29.6"
and the problem with the current error message
"cannot find Neon"
was simply that it contradicts the earlier message. So, on failure to
compile and link a test program, just make the message say something
like
"failed to compile and link a test program"
instead. That's enough to make the user look at 'config.log' for more
details.
- Julian
Re: [build error] configure error when using libneon build with no
xml support
Posted by Peter Samuelson <pe...@p12n.org>.
[Peter Samuelson]
> (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.)
Followup from IRC: we determined that the reason Doug's neon library
didn't support XML functions is, he used 'configure --without-webdav'.
If you don't say --without-webdav, the neon configure script will
indeed find an appropriate XML library or die trying.
Now ... it would be possible to detect, explicitly, that neon was built
--without-webdav, and tailor our error appropriately. But it'd be ugly
code. Is it worth it? Do other users run into this problem?
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
Re: [build error] configure error when using libneon build with no
xml support
Posted by Peter Samuelson <pe...@p12n.org>.
[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/