Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • FWIW, it's conceivable (though perhaps not likely) that upgrading to the latest version of ExtUtils::MakeMaker will heal your hurt; I've seen library-related problems described and resolved on perl.makemaker [perl.org].

    Caveat: upgrading ExtUtils::MakeMaker might (again, conceivably) introduce problems.
    • PDFLib has nothing to do with the Perl make/build process. How will upgrading EU::MM help? Although I guess you might be confusing it with my reference to PDFLib.pm, which isn't the problem.

      The problem is the binary C library, or more acurately finding the right place to put it and knowing how to link to it (via registry or the like). All the traditional routes don't seem to work. As there is sparse documentation, the manual isn't helpful.

      • There is an entry in the PDFLib manual about Perl, but it gives no indication as to why, having created auto/pdflib_pl and copied all the relavent .pm and .dll to both the site/lib and site/lib/auto/pdflib_pl directories (which is what it implies), when I try to install Matt's PDFLib Perl interface it doesn't find them.

        I see. The Makefile.PL in PDFLib.pm requires pdflib_pl and that's what's failing, right? Can you trace into pdflib_pl?