Norman,
So now the build for a component will be:
./configure;./configure dependencies;make;make install;make dist
What does ./configure dependencies do/generate then?
Additionally the old classic AUTOASTROM tar source in /classic on Saturn
does not build on FC2 i386.
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Norman Gray
Sent: 20 December 2004 11:30
To: [log in to unmask]
Subject: Re: Starlink Nightly Build On System:RHEL-WS3-3_i386
Steve,
On 2004 Dec 20 , at 11.21, Rankin, SE (Stephen) wrote:
> make configure-deps is a top-level thing isn't it, building an
> individual
> component only has make;make install;make dist?
This is true. However several of the components have dependencies on
other components such that the `configure dependencies' have to be
built before the component in question is _configured_, not just before
it is built (which is the usual relationship with dependencies).
Do I understand your component-by-component build correctly -- do you
configure and build each component in turn? If so, then you simply
need to add the configure dependencies to the network of dependencies
you build up from componentset.xml.
See you,
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|