[Debian-med-packaging] Bug#859667: libundead: FTBFS on armhf and ppc64el: tests fail

Matthias Klumpp matthias at tenstral.net
Thu Dec 14 10:53:25 UTC 2017


2017-12-14 8:29 GMT+01:00 Andreas Tille <andreas at fam-tille.de>:
> On Thu, Dec 14, 2017 at 02:06:11AM +0100, Matthias Klumpp wrote:
>> 2017-12-13 11:19 GMT+01:00 Andreas Tille <tille at debian.org>:
>> > control: tags -1 help
>> >
>> > I need to admit I have no idea how to proceed with this issue. :-(
>>
>> Please try to package the latest version of undead, or - if that is
>> not desired - request a rebuild of the package on the failing
>> architectures.
>> The library seems to have been compiled with an outdated LDC compiler there.
>
> Its completely desired to follow upstream.  I just did not noticed
> amongst all the other bugs I'm currently fixing in other packages.
>
> Unfortunately it fails to build.  I'd be more than happy if you could
> have a look at my latest Git commit.  It ends with:
> ...
> [...]
> /build/libundead-1.0.9/obj-x86_64-linux-gnu/../src/undead/stream.d:1217: undefined reference to `_D6undead3utf6toUTF8FNaNbNiNfNkJG4awZAa'
> [...]

Those issues are usually easy to fix, most often it's either some
stuff that is not linked or was compiled with the wrong D version, or
a missing source file. In this case it was the latter, I added it to
the Meson build definition and everything works.
Changes are committed to Git :-)

>> As for the ppc64el version, it might not make sense to keep that
>> around. Maybe rebuilding it on that arch will fix the issue though.
>> How to proceed on the ppc64el arch support front is currently a bit
>> unclear, because upstream doesn't really test that port:
>> https://github.com/ldc-developers/ldc/issues/2356#issuecomment-350394691
>>
>> I have a few ideas on how to address that issue potentially though (by
>> using different D compilers for different architectures, for example,
>> or by just removing the ppc64el port).
>
> In practice most packages of Debian Med are used on amd64.  So for
> practical usage this is possibly no real constraint.

I am currently planning to add a new "dcompiler" metapackage for use
in Debian packaging that will install ldc or gdc depending on the
architecture, so we have one compiler with at least some level of
upstream support on each architecture. That might be a way forward
here.

Cheers,
    Matthias



More information about the Debian-med-packaging mailing list