...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...


In reply to 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
in thread 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 2007fld

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.