Re: [greenstone-users] problems with building demo under MacOSX

From John R. McPherson
DateTue, 16 Dec 2003 08:29:47 +1300
Subject Re: [greenstone-users] problems with building demo under MacOSX
In-Reply-To (0BCFD178-2EF7-11D8-B62A-0030656FC7D6-jeremymearsdesign-com)
On Mon, Dec 15, 2003 at 11:05:59PM +1100, Jeremy Mears wrote:
> Hello,
>
> I've just started learning about Greenstone (MacOSX 2.40a, seemed to
> install fine) for a job that landed on my desk. Major newbie status
> here.

> Basically i create a new collection, then include the source data and
> then try to build. I get the following error about plugins:
> "GLI has been unable to determine the arguments for the ArcPlug plugin.
> Please ensure that the plugin in question provides the -xml flag by
> running the pluginfo.pl script described in section 2.1 of the
> Greenstone Developers Guide"
>
> That error dialog comes up for each plugin.
>
> I also get the following error log:
>
> Command: /Applications/Greenstone/bin/script/import.pl -importdir
> /Applications/Greenstone/collect/clonedem/gimport/ clonedem -archivedir
> /Volumes/Beryl II/Jobs/NHMRC
> import.pl> couldn't find diagnostic data in
> /System/Library/Perl/5.8.1/pods/perldiag.pod
> /Applications/Greenstone/collect/clonedem/perllib

[snip]

> /Network/Library/Perl/5.8.1 /Network/Library/Perl .
> /Applications/Greenstone/bin/script/import.pl at
> /System/Library/Perl/5.8.1/diagnostics.pm line 252, <POD_DIAG> line
> 617.
> import.pl> Compilation failed in require at
> /Applications/Greenstone/perllib/acronym.pm line 28, <POD_DIAG> line
> 617.

Hi,
I suspect both of your problems are really the same problem, and
greenstone's perl scripts used at import and build time are failing
(since the GLI uses them as well).


I don't have access to a mac os x machine at the moment (although I should
later today), but it looks like perl's "diagnostics" module is causing
problems. You could try editting greenstone's perl modules
"gsdl/perllib/acronym.pm" and "gsdl/perllib/plugins/BasPlug.pm" and
commenting out the line in each file that says "use diagnostics;" - you
can comment it out by adding a "#" character to the start of the line.

If that doesn't 'fix' it then there is a deeper problem that we'll have
to track down.

John McPherson