Norman,
> This is documented in SSN/78, as of revisions 1.45 and 1.46 -- let me
> know if this needs to be clearer or more prominent. I think that David
> is the only person other than me who's had to use this facility.
OK. Done it.
> * The starconf.m4 macros are now installed where aclocal/autoreconf
> expects to find extension macros, rather than being dropped into the
> working directory by the starconf application. This should be more
> robust, and has permitted a substantial simplification of the starconf
> script, but be alert for any breakage here. As I mentioned last week,
> there are a few files you can delete. Though I updated all the
> bootstrap files (I think), generally fresh checkouts or updates plus
> autoreconf should tidy things up.
"Be alert" - my watchdog senses have revealed that, after a complete new
checkout of everything, I get things like:
Bootstrapping applications/sst...
Using starconf in /stardev/cvs/star/buildsupport ...
starconf
Error: The $PATH aclocal (/stardev/cvs/star/buildsupport/bin/aclocal)
looks for extension macros in /stardev/cvs/star/buildsupport/share/aclocal
but starconf extension were installed in
.
You need to fix your path and rerun starconf
for every application. My path is
.:/home/dsb/JBuilder6/jdk1.3.1/bin:/stardev/cvs/star/bin:/stardev/cvs/star/buildsupport/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/X11R6/bin
If I ignore these messages, I get:
make[1]: *** No rule to make target `sun185.htx_tar', needed by `all-am'.
Stop.
make: *** [/stardev/cvs/star/manifests/messgen] Error 2
when doing "make world".
David
|