wall has asked for the wisdom of the Perl Monks concerning the following question:

I need to package an installer-application written in Perl 5.6.1 (HP-UX 11.00), which uses LibXML-1.53 Module.
The problem is, that on customer side, we may not have make/gcc present (and it's an overhead to install make/gcc/bison/flex). Make and GCC are 'required' for doing a perl Makefile.PL for LibXML-1.53 and other perl modules LibXML-1.53 depends upon.
Is there a way to do a 'perl Makefile.PL;make;make test; make install' on our test systems, and then use those pm files for the packaging? I tried copying the entire perl 'lib' directory, and I set my $PERL5LIB appropriately, but I still get the following error:
# /opt/perl/bin/perl -e 'use XML::LibXML' Can't find 'boot_XML__LibXML__Common' symbol in opt/perl/lib/site_perl +/5.6.1/PA-RISC1.1/auto/XML/LibXML/Common/Common.sl at opt/perl/lib/site_perl/5.6.1/PA-RISC1.1/XML/LibXML.pm line 11 Compilation failed in require at opt/perl/lib/site_perl/5.6.1/PA-RISC1 +.1/XML/LibXML.pm line 11. BEGIN failed--compilation aborted at opt/perl/lib/site_perl/5.6.1/PA-R +ISC1.1/XML/LibXML.pm line 11. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1.

If I could make an executable out of the whole application, it would be the best thing. But it's still ok if we are able to run the installer applicaiton after installing perl and libxml2 (C libraries).
I've tried using perl2exe, perlcc and perl2bin, but there is some problem or the other.
Please help.
-Wall

Replies are listed 'Best First'.
Re: Using Pre-compiled modules
by castaway (Parson) on Jan 31, 2003 at 13:06 UTC
    PodMaster suggested using PAR for that, and looking at the documentation, it seems that it should solve your problem. It involves 'make'ing the Module you want to use on one system, then zipping up the entire blib/ and lib/ directories, which contain the entire module, for use on another system.

    Other than that, as I suggested a few times: You can install/compile your perl into a completely clean directory structure, make and install the modules, and copy the complete directory structure to the new machine. (It'd better have the same architechure etc. tho :)

    We've had the second one of these working on a HP machine here.

    C.

Re: Using Pre-compiled modules
by Limbic~Region (Chancellor) on Jan 31, 2003 at 14:11 UTC
    I do this all the time as I only have one machine with a licensed version of the HPUX ANSI compiler. We do not use GCC.

    The key is to make sure the OS, version (64 or 32 bit), and RISC architecture are the same.

    If that all checks out, all you need to do is look at the 'install' portion of the generated Makefile.

    Perform the make install on the machine with gcc, then create a tar ball of ALL the files in the 'install' section.

    Hope this helps - L~R

Re: Using Pre-compiled modules
by Anonymous Monk on Jan 31, 2003 at 13:36 UTC
    what is perl2bin? all I could find through google is some stuff in german, not where to get it or anything