| [reply] |
It works fine with recompiled perl
| [reply] |
perl -V Can't locate Config.pm in @INC (you may need to install the Config module) (@INC contains: …).
powerperl, were there any directories listed there ? Or did it actually specify (@INC contains:) - in which case @INC is definitely empty.
Oddly enough, I've just been building various configurations of unthreaded perl-5.37.1 on Windows. They've all built, tested and installed without any errors but they all have an empty @INC:
>perl -V
Can't locate Config.pm in @INC (you may need to install the Config mod
+ule) (@INC contains:).
BEGIN failed--compilation aborted.
No such problem with the threaded builds of perl-5.37.1.
I've never seen the like of it before !!
However, if your @INC is not empty, then you and I are almost certainly facing different issues.
Cheers,
Rob | [reply]
[d/l]
[select] |
@INC is not empty so we are on different paths
| [reply] |
Path mentioned in @INC has Config.pm
If so, then the process has insufficient permissions to read both the directory and the file.
| [reply] |
It works fine when perl recompiled
| [reply] |
In the OP, you said the paths were in @INC. But since PERL5LIB simply adds to @INC, it appears that you were mistaken, and that was I operating under incorrect information.
So, ignore that bit about permissions. What you have is a very broken installation of Perl. You shouldn't have to tell Perl where to find Config. You should reinstall it; you shouldn't be applying hacks like using PERL5LIB.
| [reply] |
Are you on Linux? Use strace -e trace=%file perl -V to see which files Perl is trying to open and why it fails. There will be a lot of output, so make sure to read Writeup Formatting Tips and format it correctly using <code> tags. | [reply]
[d/l]
[select] |
