On Thu, Dec 01, 2011 at 09:50:15AM +0100, Arnaud Charlet wrote:
> > As written in the PR, even if you on say x86_64-linux
> > ../configure --enable-languages=c --target=i686-pc-linux-gnu
> > you end up with:
> > CONFIG_LANGUAGES = c++ lto
> > LANGUAGES = c gcov$(exeext) gcov-dump$(exeext) $(CONFIG_LANGUAGES)
> > ...
> > LANG_MAKEFRAGS = $(srcdir)/ada/gcc-interface/Make-lang.in
> > $(srcdir)/cp/Make-lang.in $(srcdir)/fortran/Make-lang.in
> > $(srcdir)/go/Make-lang.in $(srcdir)/java/Make-lang.in
> > $(srcdir)/lto/Make-lang.in $(srcdir)/objc/Make-lang.in
> > $(srcdir)/objcp/Make-lang.in
>
> Do we know why LANG_MAKEFRAGS contains all the disabled languages?
> If that a feature/requirement or a bug/limitation?
>
> If the latter, I'd rather fix the issue there if possible.
I believe because we want
cd obj/gcc
make f951
work even when --enable-languages=c,c++ , it is quite handy
not having to reconfigure gcc because you forgot one language, especially
when you have lots of cross-compilers around.
If LANG_MAKEFRAGS would be limited only to the chosen languages,
this would suddenly not work at all.
Jakub
