----- Original Message ----- From: "Ganesh Krishnan" <[email protected]>
> It exits with the following error message: > Can't locate Inline.pm in @INC (@INC As Derek has pointed out, Inline is listed as a pre-requisite for PDL. Once you've installed Inline, run that script again and see if the reference to PL_sv_yes causes any problems. If it does, then I can only think that there's something wrong with your perl. Have you been using this build for a long time ? If so, have there been any other problems building perl extensions (ie XS modules) ? > The file libperl.a does exist on my machine. perl -V:libperl produces > "libperl='libperl.a'". So I am assuming that libperl is installed. Yes, everything looks ok to me on that score. > perl -V produces the following output: [snip] > use64bitint=undef use64bitall=undef uselongdouble=undef [snip] > ivtype='long', ivsize=4, nvtype='double', nvsize=8, Your machine and OS might be 64-bit, but this is a 32-bit build of perl. Nothing wrong with that, but if you want a true 64-bit build of perl try rebuilding with: sh Configure -des -Duse64bitall That will give you 64-bit IV/UV and 96-bit NV, plus 64-bit address referencing. See the INSTALL file in the top level perl source folder for details and other options. (eg, if you want only 64-bit integers, but no long doubles and no 64-bit address referencing then you'd just 'sh Configure -des -Duse64bitint'.) Note that if you do rebuild perl in this way, any perl extensions that you've already built using the existing perl will be incompatible with this new build of perl, and will have to be recompiled. Cheers, Rob _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
