in reply to why perl doesnt recognize modules after copyied *.pm to paths in @INC

Many Perl modules include compiled components written in XS (a highly pre-processed flavour of C). Just copying across the Perl module (which in these cases is often just a stub to load the XS) is insufficient.

On a machine with Internet access, download the installation tarballs for the libraries you need (including their dependencies), then copy them to the machine you want them on. Then, making sure you install them in the correct order to satisfy any dependencies), decompress them and run:

perl Makefile.PL make make test make install

for each.

Or, as per marto's suggestion set up a local CPAN mirror. That's probably more initial work, but would pay off in the long term.

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
  • Comment on Re: why perl doesnt recognize modules after copyied *.pm to paths in @INC
  • Download Code

Replies are listed 'Best First'.
Re^2: why perl doesnt recognize modules after copyied *.pm to paths in @INC
by czkzga (Initiate) on Nov 29, 2012 at 14:25 UTC
    thx, it is important information i will check if modules have xs.