Re^3: why @INC looks for lib/5.10.0/x86_64-linux, instead of lib/perl5/site_perl/5.10.0/x86

Or you could properly install the modules. Seeing as you should do that either way, recompiling your Perl doesn't help you any.

Comment on Re^3: why @INC looks for lib/5.10.0/x86_64-linux, instead of lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi

Replies are listed 'Best First'.
Re^4: why @INC looks for lib/5.10.0/x86_64-linux, instead of lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi by Anonyrnous Monk (Hermit) on Dec 30, 2010 at 12:57 UTC
...recompiling your Perl doesn't help you any. Not necessarily true. If you build a perl that's binary compatible with the perl that was originally used with the modules, you can for sure make use of existing XS modules — provided they do work in principle, i.e. their dependent libs are installed, etc. Otherwise, as any such libs will have to be installed anyway, trying to rebuild/install the modules alone wouldn't help you any. Of course, the real question is why th OP didn't simply also copy over the perl binary that originally belonged to the modules...	[reply]

Replies are listed 'Best First'.

Re^4: why @INC looks for lib/5.10.0/x86_64-linux, instead of lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi
by Anonyrnous Monk (Hermit) on Dec 30, 2010 at 12:57 UTC

...recompiling your Perl doesn't help you any.

Not necessarily true. If you build a perl that's binary compatible with the perl that was originally used with the modules, you can for sure make use of existing XS modules — provided they do work in principle, i.e. their dependent libs are installed, etc. Otherwise, as any such libs will have to be installed anyway, trying to rebuild/install the modules alone wouldn't help you any.

Of course, the real question is why th OP didn't simply also copy over the perl binary that originally belonged to the modules...

[reply]