Re^2: How does the Perl choose between lib and lib64?

Why do I want to control this choice? Because when I install a Perl module into some central place (let's say with "lib"), then somebody tries to access it from another machine, where the same Perl looks for "lib64" - it's a disaster...

So I used to write my modulefiles with both "lib" and "lib64", so the PERL5LIB value becomes twice as long as it should be - it doesn't look right

Thanks
Alex

Comment on Re^2: How does the Perl choose between lib and lib64?

Replies are listed 'Best First'.
Re^3: How does the Perl choose between lib and lib64? by Eliya (Vicar) on Nov 11, 2011 at 20:43 UTC
As a workaround, you could make one directory a symlink to the other... (so they're effectively the same)	[reply]
Re^3: How does the Perl choose between lib and lib64? by Anonymous Monk on Nov 14, 2011 at 09:20 UTC
...then somebody tries to access it from another machine, where the same Perl looks for "lib64" - it's a disaster... Wait what other machine? Yes, what you describe sounds like a disaster indeed You should stick with one perl, and other perls shouldn't be trying to load other perls modules If you want to share modules between machines, compiled with the same version of perl... , see Re: Using a shared object in perl, CPANPLUS::Dist::RPM CPANPLUS::Dist::Deb PPM::Make PAR::WebStart ... Re: Transferring CPAN Modules between Environments So I used to write my modulefiles with both "lib" and "lib64", so the PERL5LIB value becomes twice as long as it should be - it doesn't look right Looks are overrated :\| see sitecustomize in perlrun	[reply]