Simon Josefsson <[EMAIL PROTECTED]> writes:
> http://autobuild.josefsson.org/gnulib/gnulib.html
I have improved the output, and the summary at the top of that URL
should now be more readable. It is easy to quickly spot which modules
are working and which are not. Suggestions welcome. But more
importantly -- write self tests for gnulib modules!
Possibly the rest of the page could be removed, I'm not sure it is
useful. Hm. Or better, moved to a separate page. It may be useful
when tracking down problems in older versions.
Again, if someone can run the following script on some non-i386 and/or
non-linux platform, that would be great. Of course, you'd typically
create a separate Unix user for this, and/or chroot it, if you don't
trust the gnulib CVS gnulib-tool to not do evil things to your system.
Invoke the script below with the path to a gnulib CVS checkout. Note
that the script run 'cvs update' and use $1/../build as the build
directory.
/Simon
#!/bin/sh
GNULIB="$1"
if ! test -d "$GNULIB"; then
echo "Usage: $0 <GNULIBDIR>"
exit 1
fi
GNULIBTOOL=$GNULIB/gnulib-tool
DATEFORMAT="%Y%m%d-%H%M%S"
# Update gnulib cvs.
cd $GNULIB
CVSDATE=`date "+$DATEFORMAT"`
cvs update
# Get module list.
MODULES=`$GNULIBTOOL --list`
# Iterate over modules.
for module in $MODULES; do
echo Working on module $module...
(set -x
: autobuild project... $module
: autobuild revision... cvs-$CVSDATE
: autobuild timestamp... `date "+$DATEFORMAT"`
: autobuild hostname... `hostname`
BUILDDIR=$GNULIB/../build/$module
rm -r $BUILDDIR
mkdir -p $BUILDDIR
$GNULIBTOOL --dir $BUILDDIR --with-tests --create-testdir $module
cd $BUILDDIR
./configure && make distcheck
rc=$?
cd $GNULIB
echo rc=$?) 2>&1 | mail [EMAIL PROTECTED]
done
