Your message dated Fri, 15 Dec 2017 13:53:32 +0100
with message-id
<CAKNHny_YgnVfUqVvM=yj-yz6y9fr6ypcx-lv1erpp+kwu8c...@mail.gmail.com>
and subject line Re: [Pkg-d-devel] Bug#884441: dh-dlang requires neon on armhf
has caused the Debian Bug report #884441,
regarding dh-dlang requires neon on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
884441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-dlang
Version: 0.1
Severity: serious
Tags: sid buster
the make snippet reads:
ifeq ($(DEB_HOST_ARCH),armhf)
DFLAGS += -mattr=-neon
endif
neon is not required in the armhf baseline, you must not set this flag. The
minimum fpu requirement is vfpv3-d16.
--- End Message ---
--- Begin Message ---
2017-12-15 9:46 GMT+01:00 Matthias Klose <d...@debian.org>:
> Package: dh-dlang
> Version: 0.1
> Severity: serious
> Tags: sid buster
>
> the make snippet reads:
>
> ifeq ($(DEB_HOST_ARCH),armhf)
> DFLAGS += -mattr=-neon
> endif
>
> neon is not required in the armhf baseline, you must not set this flag. The
> minimum fpu requirement is vfpv3-d16.
Well, that's exactly what this flag does - LDC is compiling with NEON
by default, on upstream's and its Debian maintainer's request, but we
don't want stuff to be compiled in Debian with the NEON extensions
enabled. Therefore, we explicitly tell LDC not to do that.
Mind the minus in front of the "neon" in that line ;-)
This code is duplicated in a lot of D packages at the moment, and
works quite well there, so I don't see the issue. Please reopen the
bug report if there really is a problem though, could be that I am not
seeing the issue here.
FWIW, I will upload a package using this today, so we'll see if the
existing build breaks or not (it really shouldn't).
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
--- End Message ---
