Your message dated Wed, 17 Jul 2024 02:54:09 +0000
with message-id <e1stunx-002f9e...@fasolo.debian.org>
and subject line Bug#1073188: fixed in dxvk 2.4-2
has caused the Debian Bug report #1073188,
regarding dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using 
-mbranch-protection=standard
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.)


-- 
1073188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dxvk
Version: 2.3.1-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: pac-bti

dxvk fails to build from source on arm64 due to the aarch64-specific
compiler flag -mbranch-protection=standard leaking into CFLAGS used by
x86_64-w64-mingw32-gcc:

 meson.build:1:0: ERROR: Unable to detect linker for compiler 
`x86_64-w64-mingw32-gcc -Wl,--version -flto -Wl,--build-id -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -mbranch-protection=standard -Wdate-time 
-D_FORTIFY_SOURCE=2`
 stdout: 
 stderr: x86_64-w64-mingw32-gcc: error: unrecognized command-line option 
‘-mbranch-protection=standard’

--- End Message ---
--- Begin Message ---
Source: dxvk
Source-Version: 2.4-2
Done: Marc Dequènes (Duck) <d...@duckcorp.org>

We believe that the bug you reported is fixed in the latest version of
dxvk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Dequènes (Duck) <d...@duckcorp.org> (supplier of updated dxvk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jul 2024 11:12:52 +0900
Source: dxvk
Architecture: source
Version: 2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau <av...@debian.org>
Changed-By: Marc Dequènes (Duck) <d...@duckcorp.org>
Closes: 1073188
Changes:
 dxvk (2.4-2) unstable; urgency=medium
 .
   [Emanuele Rocca]
   * Use amd64 CFLAGS when building on arm64 (Closes: #1073188).
   * Use x86_64-w64-mingw32-objcopy on arm64.
Checksums-Sha1:
 3d10ee720d225f4b2f9e73838aba17f08cace9c5 2415 dxvk_2.4-2.dsc
 47f2a3ab26eacdd94483470656ce847042128944 97536 dxvk_2.4-2.debian.tar.xz
 c9e710cb3eb0917c302aa11577eb764aa8fd7b4f 10700 dxvk_2.4-2_i386.buildinfo
Checksums-Sha256:
 283b83dfa17ae1173e213cd272aadb8a5bea9a587c736cbba9d95883e79546e6 2415 
dxvk_2.4-2.dsc
 7db1eb3bf1f89f11199575db8f0d76e622861f78d275f868c74920f368d24837 97536 
dxvk_2.4-2.debian.tar.xz
 911ebde0b19a82de7a78578eccfe0cc7b33bcc9f65d5ed6095f3b321e4cf0309 10700 
dxvk_2.4-2_i386.buildinfo
Files:
 918786cbd869ee427dd89932fb69740e 2415 libs optional dxvk_2.4-2.dsc
 36587955f0d9020271e0d3aa7e24e06c 97536 libs optional dxvk_2.4-2.debian.tar.xz
 8609fe6d2637c764a4e917b9fde3e1e0 10700 libs optional dxvk_2.4-2_i386.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAmaXL1oACgkQVen596wc
RD+/Kg/+Iq3NMIJ6K5KpMi2GncxEkzp8rM4+QxwgMEnnmD5OiajmmZdZHQTI4gxw
4nPJqQHqfGcWAdJP/m/3ywj9kdmFjLDlmDDpG5trwaNGew139sy5j0PQNkIK9WEc
LQm4njq/SYEP2WMpgkWqG3kcZryCwpoEVkfLSQHq+IaybfqqPAnj/kHpW+0qVEBU
m8zCrQ6BdCxwFDQ6UTNsKuSz5hdSwnXcA87/0rROTQAPUTSDe8/D31fhNg07kjTd
pElWeRebowMgxrUwAfOCQfzqfqCoxhaJdE/Q9yX5Vk6yl5F/kuLIK/X5qApqdEeu
WiEvtRYggOl3/Xp+juhNcOPNAntJhi9N9LVjMZS4kSklcpp3WkNPI7U05C1E0GgW
wRWB3MuddZKWvJPFEcMNtQ5JZ4BXq62SqpxBnu3W1Qke0b4S+lcoe3N3a5XM+uDi
kIbt9/PtgY6OkBF0/YeEsidE516L+UWGFw8B9g96bGwI7ILJGIk+AKg+NYHn/LgV
EiraSPw3//V2pSDWM240yO0ZZJdoOZUwSxXr14xcJNSVJB/azTrbHnor1il17w8f
5n7IRCiUZhNgBfHFZxxAJ++IkFd3GshrNyij6T2dyLYXCuAi7c0waO9+Utr3MTJj
4Ieje36ky+4qOJBMpP7tdMuVKTO8zyRrGnAiTNJLGu6ppxj7xOM=
=rYj4
-----END PGP SIGNATURE-----

Attachment: pgp5CJ6TnE1v6.pgp
Description: PGP signature


--- End Message ---

Reply via email to