Mark,
On 2004 Jul 8 , at 15.39, Mark Taylor wrote:
> andromeda % ./bootstrap --buildsupport-only
> Bootstrapping with
> STARCONF_DEFAULT_STARLINK = /mbt/starauto
> STARCONF_DEFAULT_PREFIX = /mbt/starauto
> BUILDSUPPORT_PREFIX = /mbt/starauto/buildsupport
> Do we need to build GNU m4? false
> Bootstrapping buildsupport:
> make -f Makefile.tmp \
> prefix=/mbt/starauto/buildsupport \
> MANIFEST=/mbt/starauto/manifests \
> buildsupport
> cd buildsupport/starconf && autoreconf --install --symlink
> cd buildsupport/starconf \
> && if test -n "$BUILDSUPPORT_PREFIX"; then \
> ./configure --prefix=$BUILDSUPPORT_PREFIX \
>> configure-output.log; \
> elif test ! -f Makefile; then \
> { t="Directory unconfigured but BUILDSUPPORT_PREFIX
> undefined";\
> echo $t >configure-output.log; echo $t >&2; \
> exit 1; }; \
> else \
> echo "No configuration necessary" >configure-output.log; \
> fi \
> && make>make.log && make install-manifest>>make.log
So now you've made _and_ installed starconf.
> andromeda % cd buildsupport/starconf
> andromeda % make
> make: Nothing to be done for `all'.
Which is correct.
> (ok then, let's try...)
>
> andromeda % ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> [...]
Now you're _re_configuring starconf, and since you haven't given the
--prefix argument which the top-level "./bootstrap --buildsupport-only"
provides when _it_ configures starconf, starconf configures using its
fallback default prefix of /star/buildsupport.
So the solution is to stop after you've done the "./bootstrap
--buildsupport-only". Alternatively, if you simply update an
already-configured starconf directory, then you can make;make install
in there. But in general the four bootstrap components (starconf,
autoconf, automake and libtool) should be configured only by the
top-level bootstrap script.
There's something of an anomaly here, yes, but it's to be expected
since this is bootstrapping the defaulting of prefixes. It would be
possible to make the starconf configure script cleverer about detecting
when these STARCONF_... variables are present, but I'm nervous of that
since there's probably enough defaulting-hoop-jumping going on already.
Does that fix things?
Norman
--
----------------------------------------------------------------------
Norman Gray / http://www.astro.gla.ac.uk/users/norman/
Physics & Astronomy, Glasgow University, UK /
http://www.starlink.ac.uk
|