On Tue, Nov 13, 2018 at 2:10 PM Alexandre Oliva <ol...@adacore.com> wrote: > > On Nov 13, 2018, Richard Biener <richard.guent...@gmail.com> wrote: > > >> Please let me know if there are objections to this change in the next > >> few days, e.g., if enabling C and C++ for an Ada-only build is too > >> onerous. It is certainly possible to rework gnattools build machinery > >> so that it uses CC and CXX as detected by the top-level configure if we > >> can't find xgcc and xg++ in ../gcc. > > > I really wonder why we not _always_ do this for consistency given we > > already require a host Ada compiler. > > Sorry, I can't tell what the 'this' refers to. Enabling C and C++ for > an Ada-only build? Reworking gnattools build machinery to use top-level > CC and CXX? Something else?
Reworking gnattools build to always use host CC/CXX in "stage1" (or for crosses) rather than doing sth different. That would also not require C++ to be enabled for crosses. > FWIW, I see the the point of using the just-built gcc/g++ if it's there > and usable: considering the checks for different versions of Ada > compilers, you really want to use the last stage of the bootstrap to > build tools linked with the runtime built with it. It seems to me you'd > run into a catch-22 without that. Yeah, but gnattools is bootstrapped, right? For --disable-bootstrap you get binaries built with the host compiler throughout and that's good. IIRC I originally stumbled across this with --disable-bootstrap. Richard. > > -- > Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo > Be the change, be Free! FSF Latin America board member > GNU Toolchain Engineer Free Software Evangelist > Hay que enGNUrecerse, pero sin perder la terGNUra jamás-GNUChe
