in reply to Module compilation hell

I understand your dispair. When I was a neophyte monk, I ran into many problems compiling modules. Occasionally, I still do. I can only offer some ideas -- unfortunately there isn't a magic bullet because modules are free, and therefore are not necessarally widely supported.

idea 1) Get gcc as your compiler. This solved 95% of my problems. After you get it, and get it working, then:

2) Compile perl with gcc. Some modules (DBI for example), prefer to be compiled with the compiler that compiled perl.

3) As noted in other replies, use perl -MCPAN and/or cpan plus. Otherwise, you will go crazy.

4) Use a newer version of perl. Modules may not play nice with older versions of perl.

These things may take you a day (or more) to get working right. Once you do, 99% of the modules will work like a charm.

good luck

-------------------------------------
Nothing is too wonderful to be true
-- Michael Faraday

Replies are listed 'Best First'.
Re: Re: Module compilation hell
by Anonymous Monk on Mar 31, 2004 at 00:03 UTC
    But I'm using Perl 5.8.1 on 3 machines - OSX Panther, Mandrake 10 and Fedora Core 1. Modules are failing to compile on all 3 machines. These are the latest OSX and Linux versions. Everything is up-to-date.
      Note that 5.8.1 was the perl that was binary incompatible.. It was incompatible to 5.8.0. That was repaired in 5.8.2. Thus I would guess that many people dont bother to test much with 5.8.1, and go straight to 5.8.2 and above. You might look to see if Fedora/OSX etc have an upgrade to 5.8.2.

      C.

        Indeed FC1 has an upgrade to 5.8.2 (released sometime before November last year), and also to 5.8.3 (as of March 25 this year). You might want to check your settings on yum / up2date to see why you're not getting those...