perl modules / RE: ParseLex

[Rob Cermak <cermak@xxxxxxxxxxxx>]

Installation of LAS on the Mandrake 10.1 system worked out just fine.  We
used as many of the perl modules that came with LAS.  Then we used the
perl-cpan system, then reverted to just downloading the most recent
version of needed modules from CPAN itself.  The newer Perl-NetCDF module
from Unidata worked much better than the one supplied with the current LAS
source code.  We had about 3 perl modules that required a *forced* 
install -- never passed all the tests.

Yes.  I recall fixing the same test programs and then ParseLex was happy.

The two sample datasets that come with Ferret/LAS work just fine with the
in-situ database sample.  We are having a devil of a time getting anything
else into LAS. 

On Thu, 3 Feb 2005, Chase, Andrew wrote:

> Hi Adam,
> 
> maybe you've already seen this, but here's an email I sent to the list awhile back about problems I was having with the ParseLex package. I think with test 4 the problem is the test itself, not the ParseLex package.
> 
> Cheers,
> Andrew
> 
> <begin old email>
> 
> I had some troubles getting the ParseLex package installed and wanted two point out to little errors I found in the ParseLex-2.15 available from cpan. The package from cpan is assumably the same as what is included in the LAS 6.4.1.0 installation that I'm working from, but went ahead and grabbed the source from CPAN to make sure I wasn't running into problems with the LAS distrobution of the package.
> 
> I've found two small errors in the ParseLex-2.15 package that were preventing me from installing it on my Fedora 3 linux machine. I'm assuming that they would affect other platforms as well, but I haven't seen any talk of it. 
> 
> In $ParseLexHome/lib/Parse/Template.pm there's two errors. The first is on line 1, 'use strict' is missing a simi colon.
> The next is on line 501, the variable $expr needs to be declared as a new variable by adding 'my' in front of it.
> broken: $expr = $1;
> fixed : my $expr = $1;
> For me, that moved the make test from 0% passing to 85.71% passing.
> Maybe the older versions of the perl interpreter were ignoring these little errors and the new one doesn't? Who knows.
> 
> The other error appears in t/test4.t and it looks like it is being caused by a change in the perl output from whatever version of perl the test was created for to the version I'm running (perl 5.8.5). The details are the same, but the formatting is different.
> 
> I read a bit about a patch for ParseLex-2.15 included in LAS, maybe I'm duplicating those efforts?
> 
> Cheers,
> Andrew
> 
> Software Engineer
> MBARI
> 
> > -----Original Message-----
> > From: Adam Baxter [mailto:Adam.Baxter@noaa.gov]
> > Sent: Thursday, February 03, 2005 7:05 AM
> > To: las_users
> > Subject: ParseLex
> > 
> > 
> > Hi,
> >     I'm working on the NOMADS project and we're trying to 
> > install LAS on 
> > one of our servers. With the help of a few of the messages on this 
> > mailing list, all of the prerequisites for LAS compile and test fine 
> > except for ParseLex on test 4. We need to somehow move 
> > forward with our 
> > installation, however and can't really wait for the next 
> > release of LAS. 
> > Is something wrong with the test or is it ParseLex itself? 
> > Can the test 
> > be safely ignored or is there possibly a patch to fix it?
> > 
> > Adam Baxter
> > Intern at NCDC/NEMAC
> > 
> 

-- 
Rob Cermak : 907-474-7948/7092 : FAX 907-474-7204 : PGP = 0x75869A6E
Software and Systems Engineer : Information Systems and Data Management
School of Fisheries and Ocean Sciences : University of Alaska Fairbanks
cermak@sfos.uaf.edu : fnjrc1@uaf.edu : ED9U1M7P01@alaska.edu