Bug#939833: default-d-compiler pointing to gdc doesn't understand the "-main" option

clone 939833 -1
reassign 939833 default-d-compiler
CCing Iain ...
On 09.09.19 14:07, Matthias Klumpp wrote:
> reassign 939833 gdc-9
> severity 939833 important
I don't think this is the appropriate action here. The GCC driver is used for
all frontends in GCC, and there won't be an option just for the D frontend in GCC.
My understanding of the default-d-compiler package is that it is an abstraction
of a D compiler driver, and that it should help with that. It's nice if you
want to put support into meson, but this should be handled at the root (and no,
I don't mean in ldc or gdc itself).
It seems to me that the correct solution is to have a ldc script doing the
option mangling for build systems other than meson. Handling gdc as a second
class citizen is not the right way to go, from my point of view.
> Am Mo., 9. Sept. 2019 um 13:30 Uhr schrieb Matthias Klose <>:
>> Package: default-d-compiler
>> Version: 0.6.3
>> Severity: serious
>> Tags: sid bullseye
>> default-d-compiler pointing to gdc doesn't understand the "-main" option,
>> causing build failures on at least, armhf and s390x during the link step with
>> the gdc command.
> That's not a problem with the metapackage, it is an issue with gdc not
> having any such option, like DMD or LDC have.
> Fortunately, this is an issue that can be worked around trivially,
> I'll submit a patch to the Meson buildsystem to fix this and also
> apply one for some of the affected packages later.
> Cheers,
> Matthias

Written by Matthias Klose 09/09/2019 15:10:01
Check some pics on this site!
22/02/2020 14:16:40