laziness, impatience, and hubris | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
but it fails to compile even after explicitly giving a path to eXpat
Yes - the Makefile.PL is not the best. I think that if you build XML::Parser the old fashioned way and begin with perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include it will work - though you may have to change (in the Makefile.PL) die <<'Expat_Not_Installed;'; to warn <<'Expat_Not_Installed;';. (I can't remember - perhaps that change only needs to be made if you build XML::Parser using CPAN.pm.) I suspect ActivePerl will also work Yes - should work. Interestingly enough, ActivePerl now works seamlessly with MinGW (and has done for a while) - and it comes with PPM already installed. This (imo) gives ActivePerl a slight edge over Strawberry Perl, at the moment. I'm hoping that future versions of Strawberry Perl will ship with both XML::Parser and the non-proprietary (CPAN) version of PPM pre-installed. That would (imo) definitely make Strawberry the more attractive option. Cheers, Rob In reply to Re: RFC: Perl-onna-Stick
by syphilis
|
|