Dan Sugalski wrote:
> That works. I'm uncertain whether we should go and skip compiler tests too,
> if the C compiler and OS versions are the same. Probably not, since a
> different C RTL version will change things.
I would say not to skip compiler checks. In fact one recent bug I found
was on a newly deployed system that had DECC installed hence configure.com
was able to determine that CC/DECC was the compiler, but the (admittedly
redundant) first check in subconfigure.com failed and left me set def'ed
to the [.UU] subdirectory. The problem was that the LMF license for
DECC had not been loaded yet, hence one couldn't compile anything in C.
It is a bug that configure.com didn't spot that problem.
> > > 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
> >
> > "-m" : skip the MANIFEST check to see that all files are present
>
> I see someone snuck that in for 5.6.0. Keen! I'd remembered the issue
> coming up, but I missed the fix.
The logic C<$ IF ;$ ENDIF> to skip the check has been in there for ages,
since folks on this list complained about how slow it was back several
years ago. It was at one time default off.
But if you think it is slow on a VAX try the same MANIFEST check under
MPW on a 68k Mac - ugghhh! (to top it off MPW regexps are quite weird).
Peter Prymmer
