Quoting Mike Pape <[EMAIL PROTECTED]>:
-- 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 `|'
This error is what I had already described in http://article.gmane.org/gmane.comp.version-control.msysgit/1473 :
Also, suddenly I get an error during building of neon/src/ saying "libtool: syntax error near unexpected token |" which is due to an empty variable global_symbol_pipe in the neon/libtool program.
Somehow this appears only if autogen.sh wasn't run in the respective directory. OTOH I'm not so sure *why* the top-level autogen.sh wouldn't also run in the src/neon directory automatically - in my installation eventually it did, and I didn't have to run it manually in the src/neon subdirectory. It could be that something failed during the top-level autogen.sh, hence it terminated prematurely but this wasn't visible enough.
But in any case I'm glad all of you eventually got it working. Congrats! Christian
