• Timo Sintonen (9/9) Jan 16 2015 This came to my mind while reading the other list.
• ketmar via D.gnu (6/16) Jan 16 2015 ah, sure it is. my build scripts patching config-lang.in, removing

"Timo Sintonen" <t.sintonen luukku.com> writes:

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?

"ketmar via D.gnu" <d.gnu puremagic.com> writes:

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=20
 natural because gdc is made with c++.
 When making a cross compiler only host c++ is needed, not the=20
 target one. C++ for the target is still built and it also=20
 requires target libc (or newlib) because of building the c++=20
 runtime library.
=20
 Does anybody know if it is possible to disable building the=20
 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.