| Sherm Pendley 2004-03-30, 7:31 pm |
| Garry Heaton wrote:
> Please don't take this as a troll as I would like to hear how other Perl
> programmers deal with failed module compilation.
I try the simplistic "install Module::Name" in the CPAN shell first. If that
fails, I check the module docs to see if Makefile.PL needs additional
switches to install properly. If it does, I use "look Module::Name" to
download and unwrap the module package, and then run Makefile.PL and
friends manually.
That covers most of the problems. Occasionally I'll need to install a C
library that the Perl module depends on.
> because module compilation is so hit and miss. I have experienced failed
> compilations of many modules lately on both Mac OSX Panther and Fedora
> Core 1 (DBD::mysql, HTML::Mason, mod_perl and others)
I can't say anything about RedHat, but I've installed DBD::mysql several
times on Panther. I've found that it's trouble-free, provided that you do
two things:
1. Apply this patch described by Ed Moy (Apple engineer):
<http://www.mail-archive.com/macosx@...g/msg05736.html>
2. Follow the instructions for providing the appropriate options to
Makefile.PL. The simplistic "install DBD::mysql" won't work; in many cases
it will fail to find the MySQL headers and libraries, and in all cases the
test scripts need to know the host/database/user/password to test with.
For HTML::Mason, the simplistic approach worked perfectly on my Panther
machine. The CPAN shell automatically found and installed all of the
dependencies, and every one of the modules' self-tests passed.
Anyway, this is mostly off-topic for this group. Try posting to
c.l.p.modules (f'ups set), or to the macosx list at lists.perl.org.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
|