On Thu, 28 Jun 2001, Jarkko Hietaniemi wrote:
> > %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)?
SDBM_File was working on Alpha VMS with DEC C 6.0 as of [EMAIL PROTECTED]
Your suspicion about portability is good for Time/HiRes on the VAX though.
> 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?
LIBRARY is the ar equivalent and it likes to squawk when asked to stuff
object files that have compiler warnings into an archive file. In this
case the squawk was a fatal error for the make equivalent. I am hoping
that a clean rebuild attempt will make this go away.
Peter Prymmer
