[Slackbuilds-users] help testing new package

Dave Woodfall dave at slackbuilds.org
Thu Jun 18 23:03:20 UTC 2020

On 16/06/20 00:31,
Greg' Ar Tourter <artourter at gmail.com> put forth the proposition:
> Hi,
> I have written a Slackbuild for NCL (https://www.ncl.ucar.edu/).
> It is quite a tricky one to compile and it doesn't exit with an error when
> make fails. The only way I have found to test if compilation fails is to
> look for the ncl binary.
> Could I ask for a few kind souls to test the slackbuild and report back if
> build fails and the error. I am interested in both -14.2 and -current,
> 32bit and 64bit. This is not for the faint-hearted as it is quite big and
> takes a while.
> note that I do not compile hdf4 and grib2 compatibility in. If people want
> to, I can test and add hdf4 but I cannot get the GRIB2 library to compile
> and anyway, ncl requires its own patched version which feels like to
> muchwork for something I cannot test myself.
> Cheers
> Greg

I've just tested on a 32bit machine and it failed to produce the
binary.  End of the output:

make[1]: Leaving directory '/root/tmp/ncl-6.6.2'
Thu Jun 18 22:57:02 CDT 2020
Finished making <Build>.
Build failed to produce the ncl binary... Aborting!
Build failed to produce the ncl binary... Aborting!

I noticed your test here:

if [[ ! -f ni/src/ncl/ncl ]] ; then

You don't need double brackets for that. [[ ]] is for regexp tests,
so you only need single [ ].

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200619/8c5f44f8/attachment.asc>

More information about the SlackBuilds-users mailing list