> > Unfortunately the Make-lang.in part is still needed when using the
> > --disable-libada configure switch so a more elaborate change is needed.
>
> Hmm, I've experimented a bit and AFAICT if `--disable-libada' is given
> without my proposed change applied, then the gnatlib stuff doesn't get
On Thu, 26 Sep 2019, Arnaud Charlet wrote:
> Unfortunately the Make-lang.in part is still needed when using the
> --disable-libada configure switch so a more elaborate change is needed.
Hmm, I've experimented a bit and AFAICT if `--disable-libada' is given
without my proposed change applied, th
Unfortunately the Make-lang.in part is still needed when using the
--disable-libada configure switch so a more elaborate change is needed.
> Remove the extraneous `install-gnatlib' invocation from within gcc/ then
> as all the gnatlib handling ought to be done in libada/ nowadays.
>
> gcc/
For some reason, presumably historical, the `install-gnatlib' target for
the default multilib is invoked twice, once via the `ada.install-common'
target in `gcc/ada/gcc-interface/Make-lang.in' invoked from gcc/ and
again via the `install-libada' target in libada/.
Apart from doing the same twic
