Re: 20031021: THREDDS download

Marcus,

>Date: Mon, 03 Nov 2003 17:35:22 -0500
>From: Marcus A Christie <address@hidden>
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20031021: THREDDS download

The above message contained the following:

> We installed Perl 5.6.1 on RH 8.0 here and netcdf-perl compiled and 
> tested just fine!  With this working I set out to see if the tests for 
> the decoders package would now work.  Alas, they still came out as NOT 
> OK.  I dug deeper into the decoders-2.4.4/src/test.pl script.  It was 
> helpful to uncomment the parts that deleted the test logs (it would be 
> helpful if the logs are only cleaned up if the tests complete 
> successfully, but if the tests fail, leave the logs there; would have 
> probably saved me half a day).  The logs indicated that the decoder 
> executables weren't being found.  That's odd, I thought, because they 
> definitely were there.  Then I noticed around line 80 or so in test.pl 
> the following lines:
> 
> if( $decoder =~ /ascii/ ) {
>          `$decoder $cdl 0000.nc < testdata` ;
> } else {
>          `$decoder $cdl 0002 < testdata.wmo` ;
> }
> 
> This was the problem.  '.' isn't in my PATH, so it wasn't finding the 
> executable.  I added './' in front of the executables in these lines:
> 
> if( $decoder =~ /ascii/ ) {
>          `./$decoder $cdl 0000.nc < testdata` ;
> } else {
>          `./$decoder $cdl 0002 < testdata.wmo` ;
> }
> 
> And it worked just fine, all the tests come out OK!  For kicks, I 
> decided to try out using the netcdf-perl built with Perl 5.8 with the 
> tests, and the tests come out just fine as well!!
> 
> So, in summary, perl 5.6.1 builds and tests perfectly the netcdf-perl 
> package.  The tests for the perl decoders packages can't possibly 
> complete, however, in their current state if one doesn't have '.' in 
> one's PATH.  Finally, it looks as though the netcdf-perl built by perl 
> 5.8 may work just fine and may only have a problem with one of the tests 
> in netcdf-perl, but not so sure about this.

Thanks for this feedback.

> Thanks for your help,

You're most welcome.

Regards,
Steve Emmerson