Issue with CPAN module installations
Status: Inactive
Brought to you by:
bantik
Menu
▾
▴
#1 Issue with CPAN module installations
Mac OS X 10.3.2
Perl is up and running
I get the error message below when I attempt to install
CPAN modules of any kind
(You get this message, because MakeMaker could not find
"/System/Library/Perl/5.8.1/darwin-thread-multi-2level/CORE/perl.h")
When I looked in the CORE directory, there was only one
file - libperl.dylib
Also, there is no file called perl.h anywhere on the
boot partition
I do see CPAN info in the Perl directory, so some
things got installed. But I cannot install the
recommended modules because of the (apparently) missing
file. Is there a workaround or a setting I need to change?
degraham@helix.nih.gov
Logged In: YES
user_id=575649
Searching for "/System/Library/Perl/5.8.1/darwin-thread-multi-2level/
CORE/perl.h" on Google returned a lot of results. You might try the
suggestion I found on http://www.nntp.perl.org/group/perl.macosx/6253
which involves editing /System/Library/Perl/5.8.1/darwin-thread-multi
-2level/Config.pm-- fixing a problem that Apple has identified with
Panther.
But it still concerns me that there is only one file in your CORE directory.
Is there something nonstandard about your Perl installation?
Logged In: NO
In terms of the Perl installation, I don't know whether is
was non-standard or not. This is the Perl installation that
comes with Panther. I haven't messed with it at all.
Logged In: YES
user_id=575649
Try this, in Terminal, and tell me what you see:
cd /
sudo find . -name "perl.h" -print
This should find all occurences of perl.h in your filesystem. It's possible
that it's not in /System/Library/Perl/5.8.1/darwin-thread-multi-2level/
CORE/ where it should be.
Logged In: NO
OK. I had previously searched for this (using the regular
find, but for invisible files as well) and hadn't found
anything. When I tried
cd /
sudo find . -name "perl.h" -print
I also got nothing returned. I even made sure I was
searching from the root of the boot partition when it didn't
work, and got the same response (nothing).