Fresh checkout, bootstrap and configure from the root directory:

% make
if test -n "/usr/local/java/jdk/bin/java"; then \
    (cd buildsupport/starconf/java \
        && make GenerateDependencies.class) \
    && /usr/local/java/jdk/bin/java -classpath buildsupport/starconf/java
\
        GenerateDependencies componentset.xml >Makefile.dependencies \
else :; fi
make[1]: Entering directory
`/export/data/timj/tmp/star/cvs/buildsupport/starconf/java'
make[1]: `GenerateDependencies.class' is up to date.
make[1]: Leaving directory
`/export/data/timj/tmp/star/cvs/buildsupport/starconf/java'
Too few arguments
make: *** [Makefile.dependencies] Error 1

If I try that again I get:

% make
make: Nothing to be done for `all'.

which is all a bit odd.

Removing all the installed buildsupport directories I then get:

% make
make: *** No rule to make target
`/home/timj/data/tmp/star/cvsbuild//manifests/adam', needed by `all'.
Stop.


So clearly those manifest files are extremely important. [and I get the
feeling I've missed something vital here]

A make clean; bootstrap then gives me:

% ./bootstrap
Bootstrapping with
    STARCONF_DEFAULT_STARLINK  = /home/timj/data/tmp/star/cvsbuild/
    STARCONF_DEFAULT_PREFIX    = /home/timj/data/tmp/star/cvsbuild/
    BUILDSUPPORT_PREFIX        =
/home/timj/data/tmp/star/cvsbuild//buildsupport
    Do we need to build GNU m4?  false
mkdir -p /home/timj/data/tmp/star/cvsbuild//bin
Bootstrapping buildsupport:
    make -f Makefile.tmp \
        prefix=/home/timj/data/tmp/star/cvsbuild//buildsupport \
        MANIFEST=/home/timj/data/tmp/star/cvsbuild//manifests \
        buildsupport
make: Nothing to be done for `buildsupport'.
Can't locate object method "path" via package "Autom4te::Request" at
/usr/bin/autom4te line 81.
autoreconf --install --symlink
Can't locate object method "path" via package "Autom4te::Request" at
/usr/bin/autom4te line 81.
Can't locate object method "path" via package "Autom4te::Request" at
/usr/bin/autom4te line 81.
autoreconf: /usr/bin/autoconf failed with exit status: 1

So which files do I remove to recover from that problem (which is
presumably because I am no longer using the starlink special autoconf
tools).

Cleaning out and starting again (without anything preinstalled in
buildsupport I get this from bootstrap:


cd thirdparty/fsf/automake \
        && ./configure --prefix=${BUILDSUPPORT_PREFIX=/star/buildsupport}
>configure-output.log \
        && make>make.log && make install-manifest>>make.log
WARNING: `autoconf' is missing on your system.  You should only need it if
         you modified `configure.ac'.  You might want to install the
         `Autoconf' and `GNU m4' packages.  Grab them from any GNU
         archive site.
cd buildsupport/starconf \
        && ./configure --prefix=${BUILDSUPPORT_PREFIX=/star/buildsupport}
>configure-output.log \
        && make>make.log && make install-manifest>>make.log
STARCONF_DEFAULT_STARLINK=/home/timj/data/tmp/star/cvsbuild/ has trailing
slash
make: *** [/home/timj/data/tmp/star/cvsbuild//manifests/starconf] Error 1
Failed to make buildsupport


I'm getting very frustrated at this point! I'm clearly doing something
wrong but it's not obvious to me. I fail to see why the presence of a
trailing slash should be treated as fatal but it clearly is. Removing the
trailing slash seems to solve things!

Finally things now seem to be building for me again. Sorry for the
frustration.

How do I do the equivalent of 'make distclean' that will clean out all
cached versions and give me a clean CVS (without having to do a whole new
checkout - the test files in autoastrom are ridiculously large - 33 MB is
a bit of over kill - can they be compressed please?)

--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj