This should have gotten CC'd to the list:
----- Start of forwarded message[s] -----
Return-path: <[EMAIL PROTECTED]>
Date: Tue, 4 Apr 2000 11:22:46 EDT
From: lane (Charles Lane) @ DUPHY4.Physics.Drexel.Edu
Message-Id: <[EMAIL PROTECTED]>
Subject: RE: [ID 20000330.044] Not OK: perl v5.6.0 on VMS_AXP V7.1
In-Reply-To: Your message <[EMAIL PROTECTED]> dated 4-Apr-2000
To: dan @ sidhe.org
Bcc: lane @ DUPHY4.Physics.Drexel.Edu
Dan Sugalski ([EMAIL PROTECTED]) writes:
> At 10:54 AM 4/4/00 -0400, Jordan Henderson wrote:
> >From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
> >>At 10:43 AM 4/4/00 -0400, Jordan Henderson wrote:
> >> >Embedding VMSPIPE.COM in VMS.C and writing it out as needed? Deja vu!
> >>
> >>Hey, the build process writes out code left and right. Why not do it at
> >>runtime too? As a backup, mind, so we can fix the default version on the
> >>fly, but still...
> >
> >Charles (Lane) began the implementation of VMSPIPE.COM by writing it out from
> >VMS.C and was convinced by Charles (Bailey) that this was not best.
> Ah. Well, I guess I haven't been paying enough attention...
>
> Sounds like a good "Don't *do* that" message is the way to go...
Then I suggest the following:
o A .FIRST section in DESCRIP.MMS that defines PERL_ROOT to the
build directory...runs in subproc so existing definition not
touched in main proc. Define a "build_perl_root" the same
way for use by INSTALL target.
o Put VMSPIPE.COM in build ARCHLIB (ex: perl_root:[lib.vms_axp.5_6_0])
early in building Perl.
o since MMK INSTALL redefines PERL_ROOT with @PERL_SETUP, one of the
first install actions should be to copy VMSPIPE to the installation
ARCHLIB from the build ARCHLIB
o check for existance of VMSPIPE.COM in safe_popen, complain
loudly if not present. We only have to check in ARCHLIB
using PERL_ROOT, so should be secure and version-sensitive.
We may have to reorder some stuff in DESCRIP.MMS to make sure that we
get the right sequence of (a) creating ARCHLIB (b) copying VMSPIPE (c)
running MINIPERL.
But this should cover:
building perl (perl_root defined to build directories)
testing perl (perl_root defined to build directories)
installing perl (perl_root defined to install directories after copy of
VMSPIPE)
running perl ->perl_root defined to install directories)
->undefined perl_root, complain loudly
embedded perl ->same as running perl
I guess the only reason for using ARCHLIB rather than
PERL_ROOT:[000000] (which is much easier to deal with during MMK runs)
is that multiple versions of Perl may share the same PERL_ROOT. The
EXEs of the different versions would have to be somewhere other than
PERL_ROOT:[000000] (or embedded) and any XS code would likely bomb
until we fix the shareable image versioning, but I suppose you *could*
do it...
Maybe we should forge ahead in blind faith that we will, eventually, get
the shareable image versioning taken care of :-)
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
------ End of forwarded message[s] ------
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
