[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn-1.0.2 configure bug

From: Ben Reser <ben_at_reser.org>
Date: 2004-05-14 21:55:38 CEST

On Wed, Apr 21, 2004 at 01:20:43PM -0700, Karl Chen wrote:
> There seems to be a bug in `configure' from the just-released
> Subversion 1.0.2 tarball with passing configuration environment
> variables to included libraries (libapr), e.g.
> ./configure
> works; but
> CPPFLAGS='-Dtest' ./configure
> fails (but worked in subversion 1.0.1)

Tobias Oetiker <oetiker+r@ee.ethz.ch> wrote this following to kfogel who
forwarded it to me which I'm not forwarding here and replying to...
> in any event, while building subversion 1.0.2 I found that you have
> supplied configure scripts produced from different versions of
> autoconf. This is fatal as soon as one tries to specify additional
> compilation flags via environment variables
> try
> CC=gcc-3.3.3 ./configure ...
> it can be helped by running
> for x in `find . -name configure.in|sed 's/configure.in//'`; do
> (echo $x;cd $x; rm -rf autom4te.cache; touch configure.in &&
> autoconf-2.58)
> done
> before releasing the tar ...

I've figured out this problem...

It comes from Mandrake's autoconf package trying to be smart. Due to
their incompatabilities Mandrake went to some effort to make autoconf
2.13 and autoconf 2.5x to install in parallel. The autoconf command is
then replaced by a wrapper that figures out which version of autoconf
will work on your configure.in file the best.

When we build our tarball we run dist.sh which runs our autogen.sh which
in turn runs the buildconf(.sh) of apr and apr-util. apr, apr-util and
expat (included in apr-util) have configure.in files that work with both
2.13 and 2.5x (though with warnings). Mandrake's autoconf wrapper was
selecting 2.13 for them and 2.5x for subversion's configure.in.

So I removed Mandrake's autoconf packages from my chroot and installed
autoconf 2.59. Unfortunately 2.59 would not handle the configure.in for
expat. Nor would 2.58. I ended up with 2.57 (which is what was used
for 1.0.1).

Once I used a source built 2.57 of autoconf I was able to get a tarball
that did not have problems with the above. So right now the RM needs a
source built autoconf 2.57 and a source built libtool 1.4.3 in order to
get a good tarball.

This should be fixed with the next release. The work around given by
Tobias can be used in the meantime. Although in my experience autoconf
2.57 is needed not 2.58.

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 14 21:56:04 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.