On Tue, 17 Jul 2012, Tim Jenness wrote:
> Date: Tue, 17 Jul 2012 08:51:02 -0700
> From: Tim Jenness <[log in to unmask]>
> Reply-To: Starlink development <[log in to unmask]>
> To: [log in to unmask]
> Subject: Re: SPLAT line catalogue building
> On Tuesday, July 17, 2012 at 1:25 AM, Peter W. Draper wrote:
> On Mon, 16 Jul 2012, Tim Jenness wrote:
> On Mon, Jul 16, 2012 at 4:06 AM, Peter W. Draper
> <[log in to unmask]> wrote:
> On Wed, 11 Jul 2012, Peter W. Draper wrote:
> On Thu, 5 Jul 2012, Tim Jenness wrote:
> I was doing the starjava kapuahi build
> and whilst everything seemed to
> work I noticed, when scrolling through the
> log, that the SPLAT build failed
> for me because it could not find jniast in
> order to build the line catalogue
> (I think).
> Not quite true, the line catalogues should be packed regardless of this
> error. The failure is in creating an index of the spectral ranges of all
> the packed lines. This is used when a scan for all lines that lie on a
> spectrum is done.
> Now I've reproduced a similar failure, it is worse than this and all the
> lines are also missing from the final jar file. I've added a fix to stop
> the build when this happens.
> but if it can't find the installed JNIAST do you need to build and
> install JNIAST before you build splat?
> Just a (working) build of JNIAST is required. No need to install.
> The SPLAT build prefers the installed version of JNIAST but that isn't
> required. The fact that your installed version was binary incompatible
> prefered caused the problem.
> Right, so for a fresh install it definitely won't work because there won't
> be JNIAST installed.
> Or does it really look in the build tree for JNIAST and I got the
> failure because I had my LD_LIBRARY_PATH containing bad entries?
It might also be the case that JNIAST isn't available for a platform, the
binary is out of date etc. In that case you would need to get JNIAST