[m-rev.] for review: keep the invocation automatically up-to-date
Julien Fischer
jfischer at opturion.com
Wed Jul 23 15:04:09 AEST 2025
On Wed, 23 Jul 2025 at 11:18, Peter Wang <novalazy at gmail.com> wrote:
>
> On Sun, 20 Jul 2025 22:44:44 +1000 Julien Fischer <jfischer at opturion.com> wrote:
> > On Sat, 19 Jul 2025 at 07:43, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
> > >
> > > The main issue I am seeking feedback on is that after this diff,
> > > making the user guide requires compiler/mercury_compile to be
> > > up to date. The other rules of doc/Mmakefile already depend
> > > on the contents of the compiler directory, but they do so only for
> > > .m files, which do not need to be built.
> >
> > There is one case where this is a problem, namely building the source
> > distribution.
> > In that case mercury_compile will not exist when we build the doc directory.
> >
>
> We also cannot assume that ../compiler/mercury_compile is executable
> when cross-compiling.
>
> I assume the solution is also to invoke the bootstrap compiler
> when CROSS_COMPILING=yes.
Presumably, something like this will do?
diff --git a/doc/Mmakefile b/doc/Mmakefile
index 8dc9d91f1..5c08915e6 100644
--- a/doc/Mmakefile
+++ b/doc/Mmakefile
@@ -172,6 +172,9 @@ ug_invocation.texi: ug_invocation.texi_date
ifdef BUILD_SRCDIST
UG_INVOCATION_DEP=
UG_INVOCATION_MC=$(MC)
+else ifdef CROSS_COMPILING
+UG_INVOCATION_DEP=
+UG_INVOCATION_MC=$(MC)
else
# We do not specify the executable extension $(EXT_FOR_EXE) here because we
# need a way to refer to the compiler that works regardless of the grade in
Are you set up to test the above?
Julien.
More information about the reviews
mailing list