Hallo Ralf, On 22 Aug 2010, at 22:09, Ralf Wildenhues wrote: > * Gary V. Vaughan wrote on Sun, Aug 22, 2010 at 04:17:49PM CEST: >> I wonder whether it is possible to write a test that looks for >> the oldest Automake and Autoconf we declare our support for, >> and rerun the relevant tests with them? That would have >> caught several of the errors I made with the m4sh patches I >> submitted over the last couple of months... > > Ah, maybe a good idea.
[[snip]] Thanks :) > #! /bin/sh > # Try out Libtool with oldest supported tools. > # Use this in a fresh directory. > set -e > > # consider using shallow clones here, to ease server load. > git clone git://git.sv.gnu.org/autoconf.git > git clone git://git.sv.gnu.org/automake.git We could pull the already bootstrapped release tarballs from an ftp.gnu.org mirror here instead. > git clone git://git.sv.gnu.org/libtool.git Of course, that doesn't test the patch series you haven't pushed yet... And running it as an Autotest inside the existing tree would get us better coverage, and obviate the need for a separate checkout of the libtool tree entirely. > mkdir inst > inst=`pwd`/inst > PATH=$inst/bin:$PATH > > cd libtool > reconfdirs=. ./bootstrap > > cd ../autoconf > git checkout AUTOCONF-2.59 > # autoreconf -vi needed here? > ./configure --prefix="$inst" > make all install > > cd ../automake > git checkout Release-1-9-6 > ./bootstrap > ./configure --prefix="$inst" > make all install > > cd ../libtool > reconfdirs="libltdl "`ls -d tests/*demo*/` ./bootstrap > mkdir build > cd build > ../configure --prefix="$inst" > make all > make -k check > > # Now, mail all output and logs to the autobuild site ... > # ... and consider cleaning up afterwards. The last bit of the script is missing ;) Cheers, -- Gary V. Vaughan (g...@gnu.org)
PGP.sig
Description: This is a digitally signed message part
