Re: switching from static Perl to Shared

can I just rebuild Perl 5.24.1 with -fPIC and -Duseshrplib then install right over my current install

Dunno ... I haven't built a static perl ... but I look forward to someone providing a conclusive answer to your question.

When you install an XS module on your static perl (let's say it's Some::Module), does an auto/Some/Module/Module.so get installed somewhere ?
If so, then I think there's a good chance that the answer to your question is "yes". But I'm guessing that no such Module.so gets installed with static perls.
Therefore, I also guess that the correct answer to your question is "no" (because I believe that a shared perl will need to load a "Module.so").

I could be wrong, but.

Cheers,
Rob

Comment on Re: switching from static Perl to Shared

Replies are listed 'Best First'.
Re^2: switching from static Perl to Shared by zentara (Cardinal) on Apr 07, 2017 at 15:05 UTC
Hi, the modules still get built and put into the Perl5lib, the only difference with static is that the Perl executable is standalone and does not require a libperl.so. I guess I will back up and just try it and report what happens. :-) What the question really is will the linking to modules change in some way if the libperl is in an external .so file rather than in one monolithic file. From the early days I always built the static Perl because the general consensus was that it loaded ever so slightly faster. I'm not really a human, but I play one on earth. ..... an animated JAPH	[reply]
Re^3: switching from static Perl to Shared by zentara (Cardinal) on Apr 07, 2017 at 16:35 UTC
Hi, I tried and it seems to have worked. I am running a shared perl now, and the modules installed with a static perl seem to be running fine. Perl just works! :-) I'm not really a human, but I play one on earth. ..... an animated JAPH	[reply]