in reply to Re: 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
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

How to get the threaded perl 5.10.0? I only found one perl5.10.0 that is not threaded...
  • Comment on Re^2: 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^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
by BrowserUk (Patriarch) on Dec 30, 2010 at 02:23 UTC

    Try here.

    Beware the duplicitous sign-up page.

    When will they learn that trying to trick people into "signing up" for promotional material does them more harm than good?

    I, for one, am far more likely to respond to a simple: "If you would agree to signing up to receive low-volume, no-obligation, promotional emails, it could greatly enhance our ability to continue producing our 'community edition' Perl".

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
by Anonyrnous Monk (Hermit) on Dec 30, 2010 at 01:57 UTC

    In case of doubt, build one yourself with the -Dusethreads configuration option, i.e.

    $ ./Configure -des -Dusethreads -Dprefix=... $ make test

    after having downloaded and unpacked the Perl sources. See also INSTALL.

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
by ikegami (Patriarch) on Dec 30, 2010 at 04:21 UTC
    Or you could properly install the modules. Seeing as you should do that either way, recompiling your Perl doesn't help you any.
      ...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...