I just tried to install Inline-0.33.tar.gz, and had problems with Inline-C
not recognizing my compiler. Here's the scenario and the problem (the
solution remains TBD):
After extracting the Inline-0.33 directory from Inline-0.33.tar.gz, I ran:
perl Makefile.PL
and got the following error message:
The C compiler 'cc -n32' was not found on your system by searching your
PATH. You can install Inline.pm without installing Inline::C. But you'll
need to install another Inline language module (like Inline::Java for
instance) to actually make any use of it.
Do you want to install Inline::C? [n]
The C compiler is determined in Inline::C's Makefile.PL like this:
my ($cc, $exe) = @Config{'cc', '_exe'};
When I compiled perl 5.6.1 for my SGI IRIX 6.5 machine, perl's Configure
script defaulted "cc -n32" for the compiler name. When the Inline::C
Makefile.PL file is run, it tries to determine whether the $cc compile
string is valid like this:
my $found = 0;
for my $lib (split /[:;]/, $ENV{PATH}) {
$found = -f "$lib/${cc}$exe" and last;
}
In my case, $cc is not a single word, and the above loop performs this test:
$found = -f "/bin/path/cc -n32" and last;
which, of course, doesn't work.
I know I could re-compile perl (don't wanna) or modify Inline::C Makefile.PL
(did), but this test should probably be changed to work with $cc strings
which are valid on a command-line but not which are not valid file names.
Thanks,
Brett
--
Brett W. Denner Lockheed Martin Aeronautics Co.
email: [EMAIL PROTECTED] PO Box 748, MZ 9332
phone: 817-935-1144 Fort Worth, TX 76101
fax: 817-935-1212
