> MCR dka100:[perl]miniperl.exe "-I[--.lib]" "-MExtUtils::Install" -e
> "pm_to_blib({split(' ',<STDIN>)},'[--.lib.auto]','')" <.MM_tmp
> cp sdbm_file.pm [--.lib]sdbm_file.pm
> set def [.sdbm]
> MMS all
> %MMS-W-GMFUTURE, Time for [---]PATCHLEVEL.H is in the future: 27-JUN-2001
> 21:32:40.00
> CC/DECC
>
>/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/Define=(SDBM,DUFF,"VERSION=""0.10""","XS_VERSION=""0.10""")/Include=([---],[---])/Optimize
> SDBM.c
> CC/DECC
>
>/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/Define=(SDBM,DUFF,"VERSION=""0.10""","XS_VERSION=""0.10""")/Include=([---],[---])/Optimize
> PAIR.c
> CC/DECC
>
>/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/Define=(SDBM,DUFF,"VERSION=""0.10""","XS_VERSION=""0.10""")/Include=([---],[---])/Optimize
> HASH.c
> If F$Search("LIBSDBM.OLB").eqs."" Then Library/Object/Create LIBSDBM.OLB
> Library/Object/Replace LIBSDBM.OLB SDBM.OBJ, PAIR.OBJ, HASH.OBJ
> %MMS-F-ABORT, For target [.SDBM]LIBSDBM.OLB, CLI returned abort status:
> %X10EE8180.
> %MMS-F-ABORT, For target DYNEXT, CLI returned abort status: %X10EE8034.
>
> so that is broken.
Since nothing that should affect the build process of the SDBM_File on
VMS has changed for months {*), by a process of elimination something
higher up in the VMS build process must have changed, right?
(*) Then again, when was the last time a VMS build on this particular
platform was attempted (and successful)?
My VMS is rusty (and never was shiny to begin with), but doesn't the
above fail in trying to replace the objects sdbm, pair, and hash in
the libsdbm archive file, and the library tool then failing because
of, ummm, %X10EE8180?
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
