On fredag 30. juli 2004, 01:02, Aubrey Hutchings wrote: > It was 2.6.11. However, the installation XML::LibXML and XML::LibXSLT > still failed (I found a fix...keep reading). CPAN prints out a number > of nasty warnings
Yup, ignorable, according to Michael, as you might have seen. > cc -c -I/usr/include/libxml2 -DDEBIAN -fno-strict-aliasing > -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 > -DVERSION=\"1.58\" -DXS_VERSION=\"1.58\" -fPIC > -I/usr/lib/perl/5.6.1/CORE -DHAVE_UTF8 -DHAVE_BLANK perl-libxml-mm.c > perl-libxml-mm.c: In function `nodeC2Sv': > perl-libxml-mm.c:968: parse error before `*' > perl-libxml-mm.c:972: `decoded' undeclared (first use in this > function) perl-libxml-mm.c:972: (Each undeclared identifier is > reported only once perl-libxml-mm.c:972: for each function it appears > in.) > make[1]: *** [perl-libxml-mm.o] Error 1 > > I googled around for a bit and found a post detailing a bug that > caused the troubles listed above with XML-LibXML v 1.58, which is the > version I am trying to install. The bug is fixed is version 1.58_1, > so I installed that version via CPAN before trying to install > AxKit. OK! I haven't seen this myself. I think I'm with 1.57, still but I suppose I'll take that as a warning an defer upgrading to 1.59 is released... :-) > (AxKit, or CPAN, I'm not sure which, tries to install the > buggy version.) That worked and XML::LibXML is now installed. I > started working to install AxKit only to discover that I was missing > packages again for XML::LibXSLT, namely libxslt1-dev and another > stable package it depended on. (I love that package search on > debian's site. Thank you for that hint!) So, after some more apt-get > voodoo, I was able to sucessfully install XML::LibXSLT. Now only > AxKit is left... Yihaaa! > The AxKit install dies when it reaches the Apache mod_perl stuff. It > can't find any of the header files required. Would this be due the > fact that I installed mod_perl via a Debian package? For now, I put > back the old AxKit debian package just to see if the perl libraries > work and they do... YES! Hehe! Well, when there's headers files missing, it is almost always due to a missing -dev... I haven't yet had any problems with paths of any kinds on Debian with foreign packages, Debian's default paths are usually flexible enough to deal with things like that. They usually mix quite well. Therefore, my first thought when bumping into such things is rarely to assume that something is in the wrong place, usually it is just missing completely. That rule may not always be a good one, though. Anyway, the only apache-related -dev I could find on my system is apache-dev, do you have that? Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
