[m-rev.] for post-commit review: a start on getting type repn info from .int files

[Peter Wang]

On Tue, 27 Jul 2021 14:50:37 +1000 "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:
> 
> >> No idea for my part.  Peter, does your memory stretch back
> >> that far?
> > 
> > The exit status of the first invocation is ignored:
> > 
> >     -$(MCM) $@
> > 
> > The second invocation forces a rebuild:
> > 
> >     if $(MCM) -r $@ > /dev/null 2>&1
> > 
> > which overwrites the .err files from the first invocation.
> 
> Yes, I know. I was asking not about the exit statuses or the .err files,
> but output to stdout and stderr. There must be some such output,
> or the redirects to /dev/null wouldn't be there. Or are the redirects
> not necessary after all?

Yes, mmc --make will produce output on standard error in addition to
a .err file. Only the contents of the .err file matter to the test
infrastructure so the redirects are purely cosmetic. It would make
sense to hide the output of the first call to $(MCM) instead of the
second call.

Peter