When updating to a new version of perl, the biggest problem I've had is getting it to include the right set of existing module directories in @INC. At times I've even hacked the problem by copying certain modules from a directory that got omitted to one that was included. My final build of Perl 5.10.1 yesterday finally got it right, so it seemed good to share how.
./Configure -Dotherlibdirs=/usr/local/lib/perl5/5.8.9:/usr/local/lib/p
+erl5/site_perl/5.8.9:/usr/local/lib/perl5/5.8.8:/usr/local/lib/perl5/
+site_perl/5.8.8:/usr/local/lib/perl5/5.8.7:/usr/local/lib/perl5/site_
+perl/5.8.7:/usr/local/lib/perl5/vendor_perl/5.8.7
Obviously, you may want more or less entries, depending on how far back your perl module libraries go. It's also good to check if all the directories in your previous perl's @INC actually exist and contain at least one module.
For directories listed in -Dotherlibdirs, both the directory named and its "platform" subdirectory (like
i386-freebsd) get included in @INC. But for responses to Configure's question about "look in other dirs", which for me offered a default of
[5.8.9 5.8.8 5.8.7], only the site_perl directory seemed to be included. So answer that question with 'none', because you've already included all the directories you want in -Dotherlibdirs.
UPDATE 9/2/09: A smart fellow on the mod_perl mailing list pointed out that XS modules (in a "platform" subdirectory like
i386-whatever) aren't guaranteed to be transferable to a higher major release, e.g., from a 5.8.x perl to a 5.10.x perl. One should re-compile them, if necessary with a
force install xyz::abc in CPAN.
UPDATE 9/6/09: Carrying libraries across major Perl versions (like 5.8.9 to 5.10.1) is a bad idea: don't do it. When I rebuilt perl 5.10.1 without the 5.8.x libraries, Dynaloader error messages that I got trying to load my Apache server with mod_perl2 went away, and all was well.
The technique described above is still useful for upgrading perl within a major level (like 5.10.1 to 5.10.2).
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.