> Thinking that maybe I should remake Makefile.dependencies as a
> first step, I tried following the instructions in SSN/78 section 4.5
> "Adding components: the final step" (!), but was left with an empty
> Makefile.dependencies file. This, I presume, is because I do not have a
> java on my path. I would suggest changing section 4.5 to emphasise that
> you need a java on your path. Maybe also change the top-level Makefile to
> bomb out a bit more flagrantly and informatively if it cannot find a
> java?
Just managed to create a new Makefile.dependencies... It took me a while
to work out how to get the top-level Makefile to take note of the fact
that I now have a java on my path. I did:
./configure --no-recursion
./bootstrap --buildsupport
at the top level but this didn't do the trick. Eventually did
cd buildsupport/starconf
bootstrap
configure
which seems to fix things. Maybe SSN/78 should specify the need for a java
earlier, for instance in section 3.2, and so hopefully avoid the need for
these gymnastics.
However... the new Makefile.dependencies still does not indicate that
atools needs trn, mag, etc, to be built first.
I suppose the quick and dirty fix for this is to declare these libraries
as build dependencies in the kaplibs configure.ac, rather than link
dependencies. But presumably there is some problem in GenerateDependencies
which should really be fixed?
David
|