The answer, as pointed out above, is that the compiled modules cannot be shared.

What I ended up doing was passing PREFIX=~/perl to the initial config program and also to CPAN. This has lead to a completely separate install for the threaded perl.

As a convenience I have linked /usr/local/bin/tperl to /home/evdb/perl/bin/perl so that it is easy in scripts to change the perl version that is used.

Pity that DBI doesn't trust itself with threads, it rather removed the point of having them for me, I'll go the trusty forking route instead....

Oh, I was running 5.8.0, 5.6.1 indeed!

--tidiness is the memory loss of environmental mnemonics

In reply to Re: Can threaded and non threaded perl share the same compiled modules? by EvdB
in thread Can threaded and non threaded perl share the same compiled modules? by EvdB

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.