Bug#944640: gtk-d: FTBFS on armel/armhf with many "multiple definition" messages

[Matthias Klumpp]

Am Mi., 13. Nov. 2019 um 08:45 Uhr schrieb Raphaël Hertzog
<raphael at offensive-security.com>:
>
> Source: gtk-d
> Version: 3.9.0-2
> Severity: important
> Tags: ftbfs
>
> Hi,
>
> can you make a new source upload to let the package migrate to testing
> please ?
>
> I also noticed that the package still fails to build on armel/armhf with
> hundreds of message like these:
>
> /usr/bin/ld: ./libgtkd-3.a(ColorSelection.o): in function `_D3std4conv110__T8textImplTAyaTAyaTPvTAyaTiTAyaTiTAyaTaTAyaThTAyaThTAyaTbTAyaTbTAyaTbTAyaTbTAyaTbTAyaTbTAyaTAxaTAyaTAxaTAyaZ8textImplFNaNfAyaPvAyaiAyaiAyaaAyahAyahAyabAyabAyabAyabAyabAyabAyaAxaAyaAxaAyaZAya':
> ./generated/gtkd/gtk/ColorSelection.d:401: multiple definition of `_DT24_D3gtk6Widget6Widget10__mixin37720setBuildablePropertyMFC3gtk7Builder7BuilderAyaC7gobject5Value5ValueZv'; ./libgtkd-3.a(Button.o):./generated/gtkd/gtk/Button.d:565: first defined here
> /usr/bin/ld: ./libgtkd-3.a(ColorSelection.o): in function `_D3std4conv110__T8textImplTAyaTAyaTPvTAyaTiTAyaTiTAyaTaTAyaThTAyaThTAyaTbTAyaTbTAyaTbTAyaTbTAyaTbTAyaTbTAyaTAxaTAyaTAxaTAyaZ8textImplFNaNfAyaPvAyaiAyaiAyaaAyahAyahAyabAyabAyabAyabAyabAyabAyaAxaAyaAxaAyaZAya':
> ./generated/gtkd/gtk/ColorSelection.d:401: multiple definition of `_DT24_D3gtk6Widget6Widget10__mixin37716buildableSetNameMFAyaZv'; ./libgtkd-3.a(Button.o):./generated/gtkd/gtk/Button.d:565: first defined here
> collect2: error: ld returned 1 exit status
> make[2]: *** [GNUmakefile:252: TestWindow] Error 1
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_build: make -j8 "INSTALL=install --strip-program=true" test shared prefix=/usr returned exit code 2
> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 255

The cause of this is a GDC bug, the bugtracker should actually have
marked this package to be affected, but somehow that isn't the case...
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944380 for
details.
I will leave this issue open until the compiler issue is resolved.

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/