This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, d] Disable D on systems where it is known not to work.
Hi Iain
> On 31 Oct 2018, at 19:35, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>
> Hi Iain,
>
>> This turns off D front-end where there's been reported bootstrap
>> problems that need further investigation. Also added a configure.tgt
>> for libphobos to allow enabling for targets where there's known good
>> runtime support backed by existing continuous integration.
>>
>> For both, this can be overridden if either D or libphobos was
>> explicitly requested by configure.
>>
>> The guards will be loosened as I go through each target configuration.
>
> on unsupported targets with --enable-languages=all, this leads to gdc
> being built. However the gdc.dg tests all FAIL like this:
>
> FAIL: gdc.dg/gdc283.d -O0 (test for excess errors)
> Excess errors:
> gdc: fatal error: cannot read spec file 'libgphobos.spec': No such file or directory
> compilation terminated.
>
> They need to check if libphobos is present first.
maybe if building D .. then libphobos should be automatic
(i.e. the opt-in/out for the targets under development is to choose to build/not build D explicitly)?
[ that would avoid having to have the UNSUPPORTED stuff in the libphobos/config.tgt too .]
would that be an adequate guard?
i.e. is there any point to build D FE without also building libphobos?
Iain