hello,
think that there is a bug in buildswishe.pl, function swishe
I guess that
$zlibdir ||= $swishdir;
$libxml2dir ||= $swishdir;
should be
$zlibdir ||= $installdir;
$libxml2dir ||= $installdir;
when I fixed this, swish-e was built with libxml2 and zlib
here is buildswishe.log, xml2-config was found
checking for xml2-config... /var/home/knihovnik/tmp/test/bin/xml2-config
checking for libxml libraries >= 2.4.3... found version 2.6.10
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for gzread in -lz... yes
in the previous case, $zlibdir resolved to "/tmp/swish-e-2.4.2" (the
path to unpacked source) but correct was "/var/home/knihovnik/tmp/test"
, Libraries have been installed in:
/var/home/knihovnik/tmp/test/lib
if the fix is correct, some piece of code from swishe function is also
not needed
my $dir = get_src( 'swishe' );
so, again many thanks to Peter Karman for buildswishe.pl, swish-e now
has libxml2 and zlib installed (i tried it) and I think this script is
very, very useful - it can ease life of many people
I am going to tar up swish-e and move it from Debian to Slackware to
test whether we can build binaries at home and upload them to ISP
roman
Peter Karman wrote:
>
> Roman Chyla wrote on 11/8/04 9:36 AM:
>
>
>>this might be wrong but it seemed to me, that buildswishe.pl did not set
>>path for xml2-config and configure missed it during compilation,
>>I tried to set PATH variable beforehand (putting path-to xml2-config in
>>it) but result was the same
>
>
>>#this is swish-e
>>configuring with:
>>/configure --prefix=/var/home/knihovnik/tmp/pokus3
>>--with-zlib=/tmp/swish-e-2.4.2 --with-libxml2=/tmp/swish-e-2.4.2
>>--disable-shared LDFLAGS='-Wl,-rpath
>>-Wl,/var/home/knihovnik/tmp/pokus3/lib:/var/home/knihovnik/tmp/pokus3:.
>>-L/var/home/knihovnik/tmp/pokus3/lib:/var/home/knihovnik/tmp/pokus3:.'
>>CPPFLAGS='-I/tmp/swish-e-2.4.2/include -I/tmp/swish-e-2.4.2/include'
>>1>>/tmp/buildswishe.log
>
>
>
> check the contents of the output log:
>
> /tmp/buildswishe.log
>
> and look for whether the configure command found libxml2 or not. it
> should look something like:
>
> checking for xml2-config... /usr/bin/xml2-config
> checking for libxml libraries >= 2.4.3... found version 2.6.7
>
>
> of course, your version will be different, but the lines should indicate
> whether libxml2 library was found or not.
>
> if it was, and the resulting binary doesn't recognize HTML2, something
> else is awry...
>
Received on Tue Nov 9 01:25:38 2004