bug? apr's configure script gets confused by $CC

I have this morning's Subversion trunk checkout (2413), with apr and
apr-util head checkouts in subdirectories as suggested in INSTALL. I
ran autogen using Debian sid's autoconf, etc.

There seems to be a bug to do with passing the $CC environment
variable from Subversion's configure script to APR's:

Without it set, things work fine:

> mbp/1 subversion-trunk$ unset CC
> mbp/1 subversion-trunk$ ./configure --enable-maintainer-mode --disable-shared
> creating config.nice
> configure: Apache Portable Runtime (APR) library configuration
> checking for APR... reconfig
> configuring package in apr now
> loading cache /dev/null
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking build system type... i686-pc-linux-gnu
> Configuring APR library
> Platform: i686-pc-linux-gnu
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... yes
> checking whether the C compiler (gcc ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> Applying APR hints file rules for i686-pc-linux-gnu
> setting CPPFLAGS to "-DLINUX=2"

With it set:

> mbp/1 subversion-trunk$ export CC=gcc
> mbp/1 subversion-trunk$ ./configure --enable-maintainer-mode --disable-shared
> creating config.nice
> configure: Apache Portable Runtime (APR) library configuration
> checking for APR... reconfig
> configuring package in apr now
> configure: warning: CC=gcc: invalid host type
> loading cache /dev/null
> checking host system type... Invalid configuration `CC=gcc': machine `CC=gcc' not recognized

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

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

> Configuring APR library
> Platform:
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... yes
> checking whether the C compiler (gcc ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> Applying APR hints file rules for

I think those messages occur because the apr script is getting called
with a command like this:

  (cd apr; ./configure 'CC=gcc')

This isn't a big problem for me but I thought you might like to know.
It might cause trouble if somebody ever specifically wants to use gcc
rather than the local cc.

(Please cc me on replies)

-- 
Martin 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org