Hi All:
Here's some more info...
When I override environment variables (like PREFIX or PERLPREFIX) on the
command line or in the top level Makefile.PL, and then run
perl Makefile.PL
or
perl Makefile.PL PREFIX=/home/gederer/usr PERLPREFIX=/usr/local/lib/perl
or
perl Makefile.PL LIB=/home/gederer/usr
those environment variables get set correctly in the top level generated
Makefile, but do not seem to get recursively propagated to the generated
Makefiles in subdirectories. Instead, the lower level Makefiles seem to
pick up values directly from the /usr/local/lib/perl/Config.pm file and
not everride them with my settings. Is this expected behavior? I would
have expected my overrides to get propagated throughout the entire PDL
build.
And yes, there do seem to be some inconsistencies in the perl/Config.pm,
but it seems to me that I should be able to override them with my own
settings.
--greg
Sisyphus wrote:
----- Original Message ----- From: "Greg Ederer" <[EMAIL PROTECTED]>
.
.
So now my question is, why does
$Config{installprivlib}
point to /nfs/depot/rhe-3.0/new_perl_package/lib/perl (which does not
even
exist)
Bloody good question. (I don't have a ready answer.)
Maybe find out what other %Config keys point to /nfs (untested, beware of
typos):
perl -MConfig="%Config" -le 'for(keys(%Config)){if ($Config($_) =~
/\/nfs/) {print "$_: $Config{$_}"}}'
and how do I change it? I assume it's picking it up from the perl
installation somehow?
There's a way of changing the %Config values. (If I've got it right)
in the Makefile.PL, immediately after the 'use ExtUtils::MakeMaker;',
something like:
--------------------
BEGIN {
$obj = tied %Config::Config;
$obj->{'installprivlib'} = 'whatever_the _appropriate_value_is';
};
--------------------
And similarly, you can override any other %Config values that need to
be overridden. (I think it has to be done in a BEGIN{} block ... and
after ExtUtils::MakeMaker, and hence Config.pm, has been loaded.)
As to whether it needs to be done only in the top level Makefile.PL,
or whether it needs to additionally be done in one or more of the
other Makefile.PL's ... well, you'll soon find out :-)
Thing is, it shouldn't really be necessary at all.
As I mentioned in my initial reply, your @INC listing is strange
(multiple listings of the same directory). Looks like that's not the
only thing that's odd. Is there a sysadmin who might be able to throw
some light on the matter ?
Cheers,
Rob
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
