-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protect fatpacked perlbrew from existing INC #387
Conversation
It's not just threaded/non-threaded that is a problem - I ended up with older PERL5LIB interfering when I ran e.g. see the output of 'perl -V' at http://www.cpantesters.org/cpan/report/9b3fbfa8-b568-11e3-928b-d94f618938b0 |
The exact code I used to create the lib dir is at https://github.com/karenetheridge/misc/blob/master/install/generic/bin/newperl (around line 121). |
ping. Could this please be fixed? It's a major stumbling block for any serious use of perlbrew. |
I haven't tested this commit as I don't know how to set up a perlbrew for devel/build.sh, but I think it might do what we need. |
Protect fatpacked perlbrew from existing INC
Thanks @dagolden ... I push a build in the develop branch: https://github.com/gugod/App-perlbrew/blob/develop/perlbrew If you could test it in your scenario, please let us know if it works. Thanks |
Thank you. If the only change is adding that line, I've been using it with a locally patched perlbrew for months, so it comes pre-tested. :-) I remembered to pack it up as a pull request after having to get a co-worker set up with perlbrew. |
When I use this code, I experience more problems... e.g. when starting off in a 5.21.1 perlbrew, and executing Built under darwin PERL5LIB and PATH are being appended to, with the original perlbrew directories remaining. |
I see this just got released in version 0.70? IT IS BROKEN.
Now local::lib libraries from other versions of perl are being mixed in, which will cause all kinds of errors, including segmentation faults. |
@karenetheridge I don't see how the original issue (%INC) is connected to having mixed PERL5LIB content... but that is indeed a breakage. |
I'm not sure either, but I initially discovered it when I edited the new code in this patch into my local installation (here: #387 (comment)). |
I found I had to modify my perlbrew to add this at the top so that I only had the system libraries (you could add vendor, too, I suppose).
Otherwise switching to/from a non-threaded perl to a threaded perl would break horribly with errors like this: