in reply to Re^7: help with "symbol lookup error" message
in thread help with "symbol lookup error" message

Yes, that's the idea.

I recommend installing all modules with cpanm and its -L option to install everything specific for an application in a separate directory.

Usually, Perl guarantees (resp. takes great care) that you can upgrade between minor versions without recompiling provided that the new version of Perl was compiled exactly as the previous version. I'm not sure whether you can actually do that. I would simply reinstall, as that is usually easier.

Replies are listed 'Best First'.
Re^9: help with "symbol lookup error" message
by Special_K (Pilgrim) on Feb 03, 2023 at 22:04 UTC
    > Usually, Perl guarantees (resp. takes great care) that you can upgrade between minor versions without recompiling provided that the new version of Perl was compiled exactly as the previous version.

    I'm not sure I follow this. When you say "recompiling", do you mean recompiling the modules? Also how would one know that the new version of Perl was compiled exactly the same as the previous version? As you said, it's probably easier to just reinstall the modules.

    Also in a directory where perl modules are installed locally, is a record created anywhere in that directory indicating what version of perl was used to do the installation, or do I need to maintain that myself via directory naming conventions and/or README files?
[reply]

      Yes, you need to know the exact compilation configuration of your old Perl version. perl -V usually outputs most of what is needed, but there may be differences in how your C compiler (now) creates code.

      There is no way to determine what Perl version a module was compiled for after the fact. I suggest naming the directory extlib-5.26.0 (or whatever) to keep track of things.

      Most likely you want to read the Coexistence with earlier versions of Perl section of the installation documentation of Perl.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom