Your message dated Fri, 18 Aug 2023 07:06:14 +0200
with message-id <3c7ebf11d9c4b8135693b0ecceccd10a034e8295.ca...@physics.uu.se>
and subject line Fixed
has caused the Debian Bug report #1042079,
regarding onednn 2.7.4-1 FTBFS on arm64
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.)
--
1042079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onednn
Version: 2.7.4-1
Severity: normal
Dear Maintainer,
Building onednn 2.7.4-1 on arm64 fails with many of the following errors:
In file included from
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/src/xbyak_aarch64_impl.cpp:17:
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:70:7:
error: ‘uint64_t’ does not name a type
70 | const uint64_t SP_IDX = 31;
| ^~~~~~~~
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:56:1:
note: ‘uint64_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include
<cstdint>’?
55 | #include <sstream>
+++ |+#include <cstdint>
56 |
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:71:7:
error: ‘uint64_t’ does not name a type
71 | const uint64_t NUM_VREG_BYTES = 16;
| ^~~~~~~~
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:71:7:
note: ‘uint64_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include
<cstdint>’?
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:72:7:
error: ‘uint64_t’ does not name a type
72 | const uint64_t NUM_ZREG_BYTES = 64;
| ^~~~~~~~
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:72:7:
note: ‘uint64_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include
<cstdint>’?
In file included from
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64_adr.h:19,
from
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64_gen.h:21,
from
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64.h:73:
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64_reg.h:96:3:
error: ‘uint32_t’ does not name a type
96 | uint32_t bit_;
| ^~~~~~~~
/<<PKGBUILDDIR>>/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64/xbyak_aarch64_reg.h:19:1:
note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include
<cstdint>’?
Build log:
https://buildd.debian.org/status/fetch.php?pkg=onednn&arch=arm64&ver=2.7.4-1&stamp=1689851490&raw=0
There is an existing bug report upstream and the issue seems to have
been fixed in onednn 3.1:
https://github.com/oneapi-src/oneDNN/issues/1600
Thanks,
Oilvier
-- System Information:
Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'),
(100, 'lunar-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-16-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: onednn
Source-Version: 2.7.4-2
Done: Timo Röhling <roehl...@debian.org>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
