apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: Version of autoconf for releases?
Date Tue, 07 Feb 2012 12:18:43 GMT
On Mon, Feb 6, 2012 at 9:55 PM, Bojan Smojver <bojan@rexursive.com> wrote:
> On Tue, 2012-02-07 at 11:31 +1100, Bojan Smojver wrote:
>> This is what I get when I run the release.sh script against 1.4.5 tag
>
> Interestingly, if I rework release.sh to use branches instead of tags
> and give it 1.4.x as an argument, everything turns out clean with F-16
> defaults:
> ---------------
> Eliminating unwanted files (e.g. .cvsignore) and generating initial
> files via buildconf ...
>
> buildconf: checking installation...
> buildconf: python version 2.7.2 (ok)
> buildconf: autoconf version 2.68 (ok)
> buildconf: libtool version 2.4 (ok)

Please use clean builds of the the autoconf and libtool versions that
Graham used.  I hate seeing the autotools versions jumping around as
different people handle T&R.

> buildconf: copying libtool helper files using /usr/bin/libtoolize
> buildconf: creating include/arch/unix/apr_private.h.in ...
> buildconf: creating configure ...
> buildconf: generating 'make' outputs ...
> buildconf: rebuilding rpm spec file
> ---------------
>
> Build from the tarball works fine. So, maybe that's the ticket after
> all.
>
> PS. 0.9.x is broken, but not too worried about that.
>
> --
> Bojan
>



-- 
Born in Roswell... married an alien...

Mime
View raw message