Uwe Galle writes:
> Hi,
>
> I downloaded SimpleServer 1.0.2 and tried to install
it on Windows
> Server 2003. After the first step
>
> perl makefile.pl
>
> I got the following messages:
>
> 'yaz-config' is not recognized as an internal or
external command,
> operable program or batch file.
> 'yaz-config' is not recognized as an internal or
external command,
> operable program or batch file.
> 'yaz-config' is not recognized as an internal or
external command,
> operable program or batch file.
>
> ERROR: Unable to call script: yaz-config
> If you're using a YAZ installation from the Debian
package "yaz", you
> will also need to install "libyaz-dev" in
order to build the
> SimpleServer module.
>
> The yaz version 2.1.28 is installed on this server. It
was
> installed as Windows binary. After taking a look at
this script I
> saw that it tries to invoke the script yaz-config:
>
> my $yazconf = "yaz-config";
> my $yazver = `$yazconf --version`;
>
> But the Windows version of yaz does not contain a
script
> yaz-config.* anywhere - I searched both logical drives
beginning
> from root of my server.
Correct.
> I found the hint that yaz-config is generated after
./configure in
> the UNIX documentation
> (http://www.indexdata.dk/yaz/doc/in
stallation.unix.tkl#installation.source.unix). That
> means that even compiling yaz on Windows will not help
- because
> the built process on Windows does not contain the
./configure
> step. Indexdata provides an already configured
makefile for this
> process.
Also correct.
> I am amazed about that, also because Indexdata claims
on its
> Website "We've run through the exercise of
compiling SimpleServer
> under windows, and it turned out to be fairly trivial.
The included
> Perl makefile will work with MS VC++. The YAZ DLL is
> required. We've no reason to suspect it wouldn't run
under both
> Win98 and WinNT/2000." (http://www.index
data.dk/simpleserver) It
> is not only not trivial, it is impossible.
Strong words indeed.
> Of course the Makefile.pl suggests that yaz-config is
only
> necessary to get the version, the include and library
path of
> yaz. That's why I replaced the second of the above
two statements
> by
>
> my $yazver = '2.1.28';
>
> Furthermore I uncommented the lines under the comment
"# For
> Windows use", replaced the include and library
paths with the
> actual of my yaz installation and moved them to the
top of the
> script before "if (!$yazver || (!$yazinc
&& !$yazlibs)) {die qq[
> ...":
>
> my $yazinc = '-ID:\Programme\YAZ\include';
> my $yazlibs = 'D:\Programme\YAZ\lib\yaz.lib';
That all looks OK.
> After that, the first step "perl
makefile.pl" seems to finish
> successfully. The last lines of the nmake output are
>
> Creating library
blib\arch\auto\Net\Z3950\SimpleServer\SimpleServer.lib
and object
blib\arch\auto\Net\Z3950\SimpleServer\SimpleServer.exp
> D:\Programme\Perl\bin\perl.exe
-MExtUtils::Command -e chmod 755
blib\arch\auto\Net\Z3950\SimpleServer\SimpleServer.dll
> D:\Programme\Perl\bin\perl.exe
-MExtUtils::Command -e cp SimpleServer.bs
blib\arch\auto\Net\Z3950\SimpleServer\SimpleServer.bs
> D:\Programme\Perl\bin\perl.exe
-MExtUtils::Command -e chmod 644
blib\arch\auto\Net\Z3950\SimpleServer\SimpleServer.bs
> D:\Programme\Perl\bin\perl.exe
"-Iblib\arch" "-Iblib\lib"
Makefile.new.PL Makefile.new
> Writing Makefile for Net::Z3950::SimpleServer
>
>
> But the second step "nmake test" ends up
with
>
> D:\Programme\Perl\bin\perl.exe
"-Iblib\lib" "-Iblib\arch" test.pl
> 1..1
> Can't load
'blib\arch/auto/Net/Z3950/SimpleServer/SimpleServer.dll'
for module Net::Z3950::SimpleServer: load_file:The specified
module could not be found at
D:\Programme\Perl\lib/DynaLoader.pm line 230.
> at test.pl line 11
> Compilation failed in require at test.pl line 11.
> BEGIN failed--compilation aborted at test.pl line 11.
> NMAKE : fatal error U1077:
'D:\Programme\Perl\bin\perl.exe' : return code '0x2'
> Stop.
>
> I checked that the SimpleServer.dll exists in the path
>
D:\Programme\Net-Z3950-SimpleServer-1.02\blib\arch\auto
\Net\Z3950\SimpleServer. It
> seems that the problem is caused by the / in the path
to this
> dll. Actually there is a mix of \ and / in this path
so that
> Windows will probably have problems to process this.
What makes you think that the mixture of slashes is the
problem?
Could the problem be that the library path is relative
rather than
absolute, and you're running the script in a directory from
which the
relative path doesn't work? (I am flying blind here since
I don't use
Windows for serious work.)
> I believe that I have to change the path to
SimpleServer.dll. How
> can I do this?
As far as I can see, that's a question of configuring
Windows (and
specifically your Perl installation on Windows) rather than
about
SimpleServer specifically.
Have you successfully built and tested other CPAN modules
that have a
C component on this box?
> Do I have to change other settings?
Don't know.
> Is there any description for the Windows built process
anywhere?
Not that I know of. Please feel free to contribute one 
_/|_
____________________________________________________________
_______
/o ) \/ Mike Taylor <mike indexdata.com> http://www.miketaylor.or
g.uk
)_v__/\ Cab driver to Groucho Marx: "Have a nice
day"; Marx: "I'll have
the hell sort of day I want"
_______________________________________________
Net-z3950 mailing list
Net-z3950lists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/n
et-z3950
|