Mark,
On 2004 Aug 2 , at 12.42, Mark Taylor wrote:
> On Mon, 2 Aug 2004, Norman Gray wrote:
>
> Not sure where you mean this, but the following:
>
> % rm -rf thirdparty/fsf buildsupport
> % cvs update -d thirdparty/fsf buildsupport
> % ./bootstrap --buildsupport
> % grep STAR_EXTRA `find thirdparty/fsf buildsupport -name
> Makefile.in`
>
> gives me plenty of output:
>
> thirdparty/fsf/autoconf/bin/Makefile.in:STAR_EXTRA_DIST =
> thirdparty/fsf/autoconf/bin/Makefile.in: $(STAR_EXTRA_DIST)
> thirdparty/fsf/autoconf/doc/Makefile.in:STAR_EXTRA_DIST =
> thirdparty/fsf/autoconf/doc/Makefile.in: $(STAR_EXTRA_DIST)
> thirdparty/fsf/autoconf/Makefile.in:STAR_EXTRA_DIST =
> ...
>
> is that wrong?
Silly on my part, because I've forgotten to redo these. I'll fix those
later today, but it appears that they happen not to cause a problem in
autoconf. It seems the STAR_EXTRA_DIST references do cause a problem
within libtool, so as long as you don't have them there, you should be
OK.
> Anyway, I've done s/STAR_FC_LIBRARY/LDFLAGS/ in ccdpack/configure.ac
> (and committed it) and it seems to build OK for me on RH9.
Good.
> The resulting
> Makefile.in's in ccdpack and its subdirectories (again, following a
> checkout from scratch of these directories) reference STAR_EXTRA_DIST
> too.
Yes, they should -- including that is triggered by the presence of
STAR_DEFAULTS in configure.ac. Or rather, since STAR_EXTRA_DIST has
been in there for quite a long while now, the suppression of
STAR_EXTRA_DIST is newly triggered by the absence of STAR_DEFAULTS.
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|