On Oct 13, 2010, at 12:03, David Weintraub wrote: > I was able to build everything until neon. There I get > > $ ./configure --with-expat=/app/fms/build/lib/libexpat.la > --enable-shared=yes --prefix=/app/fms/build > checking for a BSD-compatible install... ./install-sh -c > checking for gcc... gcc > checking for C compiler default output file name... > configure: error: in `/app/fms/build/subversion-1.6.13/neon': > configure: error: C compiler cannot create executables > See `config.log' for more details. > cmu...@fmsdwbap01:~/subversion-1.6.13/neon > $ > > Can you give me any help? It looks like it's crapping out when it is > trying to determine the default link output. However, apr, apr-util, > and expat all worked.
[snip] > configure:2670: checking for C compiler default output file name > configure:2692: gcc -l/app/fms/build/include/ -brtl conftest.c >&5 > gcc: '-b' must come at the start of the command line Looks like neon is using gcc in a way that's not compatible with AIX's version of gcc. A quick Google search shows this possible solution: http://mailman.mit.edu/pipermail/kerberos/2007-June/011788.html You may want to report this problem (and the solution, if it works) to the developers of neon. Or, check if the latest version of neon is still affected; I see you're using 0.28.6 but the current version is 0.29.4. Or, check if this is an autoconf problem; rerun the latest autoconf over neon's files and see if that fixes it up.
