[m-rev.] for review: update README.macOS.md

[Julien Fischer]

On Wed, 14 May 2025 at 14:26, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
>
>
> On Wed, 14 May 2025 14:16:22 +1000, Julien Fischer <jfischer at opturion.com> wrote:
> > -Versions of macOS prior to 10.9 are not supported.
> > +Versions of macOS prior to 10.9 are not supported. Both Intel and Apple Silicon
> > +Macs are supported, although the latter has not been extensively tested.
>
> I would change both sentences to use the active voice, with "Mercury supports ...".

Done.

> > @@ -49,18 +49,18 @@ or
> >
> >  depending on their preferred compiler. In either case, every invocation
> >  of the selected C compiler on Mercury-generated C files will specify
> > -the `-m32` option. The reason for the limitation to 10.14 is that
> > +the `-m32` option. The reason for the restriction to version 10.14 is that
> >  32-bit executables are not supported at all from macOS 10.15 onwards.
>
> Again, switch to active voice, and say that it is *Apple* that does not support
> 32-bit executables on those versions.

Done, I've said macOS rather than Apple.

> >  If, after installing Mercury, you encounter errors about missing `.mih` files,
> > -and you have fink installed, then try removing the fink components from your
> > -`PATH` (these usually start with `/sw`) and reinstalling.
> > +and you have fink installed,try removing the fink components from your `PATH`
> > +(these usually start with `/sw`) and reinstalling.
>
> How can fink interfere with .mih files? If the answer is not too complex, it would be
> worthwhile including it here.

That text is over 15 years old and was written by Ian MacLarty.  In
the log message, he
says :

     I had this problem and removing fink from my PATH fixed it (though I don't
    know why).

I don't know why either.

> Also, add a space the command and "try".

Done.

Julien.