H. wrote:
!As you could have read in Jarkko's announcement, I've taken up the
Configure
!pumpin for 5.9.0
!
!I don't have VMS, nor VMS experience, and talked to Dan Sugalski about how
to
!deal with possible VMS issues. This list was the way to go in his opinion.
!
!The first thing I did was to backport Hugo's changes in Configure to the
!metaunits, and recreate Configure, config_h.SH, and the Posting/ files
from
!that. All still works a week after for most of us, so I didn't brake
anything
!(yet). I didn't check Configure.com yet.
!
!Any chance I missed something?
I have not had an opportunity to review the changes that you and Hugo
have introduced but I can answer the question that you pose with a general
"yes - it is possible that you missed something". Perhaps a table of
analogs
would be helpful:
Unix/POSIX VMS
Configure configure.com
config_h.SH same file config_h.SH
(unix gets config.h via sh) (VMS uses config_h.SH to get config.h via
vms/munchconfig.c)
config.sh (extracted) config.sh (extracted)
Config.pm (from config.sh) Config.pm (from config.sh)
Makefile.SH vms/descrip_mms.template
Makefile (extracted) descrip.mms (extracted)
hints/$osname.sh no analog all logic in configure.com
ext/util/make_ext configure.com writes out
ext/util/make_ext.com a file not shipped
In general if you introduce a new config.sh variable it would be
necessary to add it to configure.com so that the VMS
version of config.sh sees the correct value ($d_{funcname},
$i_{headername} = [define,undef], etc.) and the VMS build
does not break. Ordinarily a note to vmsperl can take care of
that ahead of time, but in practice a lot times a bleedperl
kit is released and must be patched for VMS to catch up.
!Until now, Jarkko created the Porting/ files from a completely different
!machine than I use, so all the supposed defaults will have changes (HP-UX
is
!something quite different than OSF)
The metaconfig mechanism is not in use on VMS at all.
configure.com is hand coded to address variations across
VMS and compiler version differences. There are no DCL units to
be assembled for generating configure.com.
See also:
http://pvhp.best.vwh.net/vms/configure_com_faq.html
I hope that helps.
Peter Prymmer
