neon configure fails with CC set?

Yes

I know this sounds weird, and it is weird too.

If I set the environment variable CC before I run the top-level subversion
configure script, then the neon configure script fails with the output shown
below.

If I don't set CC, the db configure script fails to detect my gcc and instead
stops on my non-working cc compiler...

So, if I edit my $PATH (to not include the dir with my faulty cc) and don't
have CC set, I can run subversion's configure successfully!

--------- neon configure output snip ---------
checking host system type... Invalid configuration `CC=gcc': machine `CC=gcc'
not recognized

checking build system type... Invalid configuration `CC=gcc': machine
`CC=gcc' not recognized

checking for ranlib... ranlib
checking for ld used by GCC... /usr/ccs/bin/ld
checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
checking for BSD-compatible nm... /usr/ccs/bin/nm -p
checking whether ln -s works... yes
updating cache /dev/null
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
configure failed for neon
------------ end of snip -------------

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org