develooper Front page | perl.perl5.porters | Postings from November 2004

Re: [PATCH] Re: getting Config.pm on a diet

Thread Previous
From:
Craig A. Berry
Date:
November 30, 2004 07:07
Subject:
Re: [PATCH] Re: getting Config.pm on a diet
Message ID:
p06110429bdd22c70d147@[172.16.52.1]
At 12:00 AM -0500 11/30/04, John E. Malmberg wrote:
>Note: I think I only get mail on the vmsperl@perl.org list.
>
>Nicholas Clark wrote:
>>On Mon, Nov 29, 2004 at 01:58:52PM -0600, Craig Berry wrote:
>> I'm not sure. I was trying to keep Config's AUTOLOAD as simple as possible.
>>Then again, using %INC shouldn't be that hard.
>>
>>For the Unix Makefile I hit the same problem (with the POD scripts) and
>>the solution I found was to change the -I on the command line from a
> >relative to an absolute path.

We could do that, but I can't find any evidence that the Unix build
is currently doing that for pod, x2p, or utilities.  For all of
these, the build descends into the subdirectory and runs the
auxiliary Makefile, passing -I../lib to miniperl.  I think the only
reason the utilities build still works on Unix is that when the
scripts do a chdir, they are changing to the directory where we
already are.  So they are essentially noops, and if they did actually
do something, the Unix build would have the same problem the VMS
build is currently having.

It usually leads to the fewest surprises to just do what the Unix
build does, so one of these days I will modify the utilities build to
run with -I../lib.

>A VMS specific method would be to have a logical name that equated
>to a search list.

@INC is a search list on all platforms.  In addition, on VMS,
PERL5LIB can be created as a search list logical name.  The problem
here though is that an individual item in the list that is sufficient
to locate a library at compile time is not sufficient to locate an
additional piece of that library at run time if a script has done a
chdir in the interim.

>My preference in doing VMS builds of application is to use the
>search list feature of logical names to isolate the source from the
>resulting binaries and intermediate files.

snip

>This does not work if the build procedure is expecting to actually
>modify files from the original distribution in place.
>
>Perl at the last time I attempted a build on VMS could not use such
>a search list.

It's a nice trick for keeping the original source pristine. We could
look into making this work for Perl but that's a different topic.
-- 
________________________________________
Craig A. Berry
mailto:craigberry@mac.com

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About