Dan Sugalski wrote:
> I'm going to be messing about in perl's guts again next week. The big VMS
> things I'm planning on are getting the non-compiling things compiling on
> VMS (perl's malloc, Ithreads, a MULTIPLICITY build) and making
> configure.com take and save defaults, with symbol overrides. I'll add in a
Sounds good - perhaps both a config.com and a Policy.com?
> question to make it skip the manifest check as well. (That should speed
> things up for multiple rebuilds, especially on VAXen) If we're lucky we
This is already in there, check the help:
$ @ Configure "-h"
Usage: @[PERL-5_6_0]CONFIGURE [-dehmrEKOSV] [-fconfig.sh] [-Dsymbol]
[-Dsymbol=value]
[-Usymbol] [-Usymbol=]
"-d" : use defaults for all answers.
"-e" : go on without questioning past the production of config.sh. *
"-f" : specify an alternate default configuration file.
"-h" : print this help message and exit (with an error status).
"-m" : skip the MANIFEST check to see that all files are present
"-r" : reuse C symbols value if possible (skips costly nm extraction).*
"-s" : silent mode, only echoes questions and essential information.
-"D" : define symbol to have some value: *
-"Dsymbol" symbol gets the value 'define'
-"Dsymbol=value" symbol gets the value 'value'
-E : stop at the end of questions, after having produced config.sh. *
-K : do not use unless you know what you are doing.
-O : let -D and -U override definitions from loaded configuration file. *
-S : perform variable substitutions on all .SH files (can mix with -f) *
-"U" : undefine symbol: *
-"Usymbol" symbol gets the value 'undef'
-"Usymbol=" symbol gets completely empty
-V : print version number and exit (with a zero status).
%Config-I-VMS, lower case switches must be enclosed
-Config-I-VMS, in double quotation marks, e.g.:
-Config-I-VMS, @Configure "-des"
-Config-I-VMS, * indicates switch may not be fully implemented for VMS.
So use:
@ Configure "-desm"
to do an autoconf autopilot style configure with MANIFEST skipping on VAXen.
Here is an example:
$ @ configure "-desm"
First let's make sure your kit is complete. Checking...
Looks good...
Operating system name? [VMS]
%Config-I-VMS, (-25200) Is this UTC Time Zone Offset correct? [y]
What is your architecture name? [VMS_AXP]
Will you be sharing your PERL_ROOT with a VAX? [n]
Installation prefix to use (for PERL_ROOT)? [ DKB100:[PERL-5_6_0.] ]
%Config-I-VMS, Skip the remaining "where install" questions? [y]
Invoke perl as a global symbol foreign command [y]
Getting the current patchlevel...
it is quite fast (on an Alpha). Give it a shot.
> should also be able to build a PERLSHR with sane image IDs and major/minor
> version numbers so we can finally skip the whole "rebuild the world every
> perl point release upgrade" thing. That and so I can finally ship prebuilt
> module kits, amongst other things.
>
> I know Peter's planning on abusing configure and subconfigure horribly (Go,
> Peter! :) so does anyone else have any other goodies they'd like? Now'd be
> the time to ask...
Hehe ;-)
Peter Prymmer
