/var/tmp/portage/sys-fs/loop-aes-3.7q-r1/work/loop-AES-v3.7q/tmp-d-kbuild/patched-loop.c:109:11: fatal error: linux/ioctl32.h: No such file or directory 109 | # include <linux/ioctl32.h> | ^~~~~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-libressl_abi32+64-20201012-091521 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.265_p01 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Sat Oct 17 10:05:17 PM UTC 2020 /var/db/repos/libressl Fri Oct 9 07:35:07 PM UTC 2020 emerge -qpvO sys-fs/loop-aes [ebuild N ] sys-fs/loop-aes-3.7q-r1 USE="-extra-ciphers -keyscrub" CPU_FLAGS_X86="aes -padlock"
Created attachment 666386 [details] emerge-info.txt
Created attachment 666389 [details] emerge-history.txt
Created attachment 666392 [details] environment
Created attachment 666395 [details] etc.portage.tbz2
Created attachment 666398 [details] sys-fs:loop-aes-3.7q-r1:20201017-222837.log
Created attachment 666401 [details] temp.tbz2
This report did not include kernel version, but I think that is the culprit - I can reproduce the error with gentoo-sources-5.9.*. This has been labeled as related to https://bugs.gentoo.org/732648, but I do not think it has anything to do with the autoconf beta. gentoo-sources-4.19.* + gcc-10 + sys-devel/autoconf-2.70_beta3 = no problem gentoo-sources-5.4.* + gcc-10 + sys-devel/autoconf-2.70_beta3 = no problem gentoo-sources-5.5.* + gcc-10 + sys-devel/autoconf-2.70_beta3 = no problem gentoo-sources-5.9.* + gcc-10 + sys-devel/autoconf-2.70_beta3 = ioctl32.h error gentoo-sources-5.8.* + gcc-10 + sys-devel/autoconf-2.70_beta3 = different(!) error There is a newer version of loop-aes available, loop-aes-3.7s, which works for me for all gentoo-sources versions in the tree; will submit a PR shortly.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6903651949519237985f9b0d4413e10748de9f1c commit 6903651949519237985f9b0d4413e10748de9f1c Author: Hank Leininger <hlein@korelogic.com> AuthorDate: 2020-11-11 00:42:37 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-11-11 07:55:48 +0000 sys-fs/loop-aes: version bump to 3.7s Updated upstream version supports 5.8.* and 5.9.* kernels. Signed-off-by: Hank Leininger <hlein@korelogic.com> Closes: https://bugs.gentoo.org/749840 Package-Manager: Portage-3.0.9, Repoman-3.0.2 Closes: https://github.com/gentoo/gentoo/pull/18220 Signed-off-by: Joonas Niilola <juippis@gentoo.org> sys-fs/loop-aes/Manifest | 1 + sys-fs/loop-aes/loop-aes-3.7s.ebuild | 71 ++++++++++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+)
(In reply to Hank Leininger from comment #7) > This report did not include kernel version, but I think that is the culprit > - I can reproduce the error with gentoo-sources-5.9.*. the attached emerge-history.txt should contain the info ?
