This came to my mind while reading the other list.
Compiling gdc automatically enables compiling c++. This is natural because gdc is made with c++.
When making a cross compiler only host c++ is needed, not the target one. C++ for the target is still built and it also requires target libc (or newlib) because of building the c++ runtime library.

Does anybody know if it is possible to disable building the target c++ compiler?

On Fri, 16 Jan 2015 17:04:16 +0000
"Timo Sintonen via D.gnu" <d.gnu@puremagic.com> wrote:

> This came to my mind while reading the other list.
> Compiling gdc automatically enables compiling c++. This is
> natural because gdc is made with c++.
> When making a cross compiler only host c++ is needed, not the
> target one. C++ for the target is still built and it also
> requires target libc (or newlib) because of building the c++
> runtime library.
> 
> Does anybody know if it is possible to disable building the target c++ compiler?
ah, sure it is. my build scripts patching config-lang.in, removing "c++" from "lang_requires_boot_languages"

i don't know what bad consequences may arise from that, but for my local builds i don't really care.