On Jan 31, 2008 5:56 PM, Johannes Schindelin <[EMAIL PROTECTED]> wrote: > Hi, > > On Thu, 31 Jan 2008, Johannes Schindelin wrote: > > > Will have a look, > > I had a look. Unfortunately, it seems that the fix for neon was not > enough: > > -- snip -- > make[1]: Entering directory `/src/subversion/subversion-1.4.6/neon' > make[2]: Entering directory `/src/subversion/subversion-1.4.6/neon/src' > /bin/sh ..//libtool --quiet --mode=link gcc -no-undefined -rpath /lib > -version-info 25:5:0 -export-symbols-regex '^ne_[^_]' -o libneon.la > ne_request.lo ne_session.lo ne_basic.lo ne_string.lo ne_uri.lo ne_dates.lo > ne_alloc.lo ne_md5.lo ne_utils.lo ne_socket.lo ne_auth.lo ne_redirect.lo > ne_compress.lo ne_207.lo ne_xml.lo ne_props.lo ne_locks.lo ne_xmlreq.lo > ne_acl.lo ne_stubssl.lo -lz > /src/subversion/subversion-1.4.6/apr-util/xml/expat/lib/libexpat.la > ..//libtool: eval: line 4170: syntax error near unexpected token `|' > ..//libtool: eval: line 4170: `/bin/nm -B .libs/ne_request.o > .libs/ne_session.o .libs/ne_basic.o .libs/ne_string.o .libs/ne_uri.o > .libs/ne_dates.o .libs/ne_alloc.o .libs/ne_md5.o .libs/ne_utils.o > .libs/ne_socket.o .libs/ne_auth.o .libs/ne_redirect.o .libs/ne_compress.o > .libs/ne_207.o .libs/ne_xml.o .libs/ne_props.o .libs/ne_locks.o > .libs/ne_xmlreq.o .libs/ne_acl.o .libs/ne_stubssl.o | | > /bin/sed -e '/^[BCDGRS] /s/. /s/.. /s/.DS_Store /s/.TemporaryItems > /s/.Trashes /s/._.TemporaryItems \([^ ]*\)/\1 DATA/' | /bin/sed -e > '/^[AITW] /s/. /s/.. /s/.DS_Store/s/.TemporaryItems /s/.Trashes > /s/._.TemporaryItems //' | sort | uniq > .libs/libneon.exp' > make[2]: *** [libneon.la] Error 1 > make[2]: Leaving directory `/src/subversion/subversion-1.4.6/neon/src' > make[1]: *** [subdirs] Error 2 > make[1]: Leaving directory `/src/subversion/subversion-1.4.6/neon' > make: *** [external-install] Error 1 > -- snap -- > > I found "export-symbols-regex" in neon/configure, and in > neon/src/Makefile. Could it be that we have to call autogen.sh also in > $d/neon/? > > Ciao, > Dscho > >
At least I know I'm not the only who got that message... I think I was thinking autogen.sh in the root directory would take care of running it. If that's not the case, that sounds like the right option as long as it forces a run of autoconf and doesn't skip it if the Makefile is there or something. Sorry about that.
