Summary: | app-crypt/loop-aes-losetup-2.35.2 - fails to compile: (no error message) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Hank Leininger <hlein> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint, sam |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/34121 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 870412 | ||
Attachments: |
emerge-info.txt
app-crypt:loop-aes-losetup-2.35.2:20220917-122915.log emerge-history.txt environment etc.portage.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2022-09-17 14:18:37 UTC
Created attachment 807526 [details]
emerge-info.txt
Created attachment 807529 [details]
app-crypt:loop-aes-losetup-2.35.2:20220917-122915.log
Created attachment 807532 [details]
emerge-history.txt
Created attachment 807535 [details]
environment
Created attachment 807538 [details]
etc.portage.tar.bz2
Created attachment 807541 [details]
temp.tar.bz2
Confirmed, can't build loop-aes-losetup with CC=clang However, loop-aes-losetup basically just builds a modified losetup from util-linux. And I get the same failure trying to build current util-linux with CC=clang. loop-aes-losetup can't be fixed until util-linux has been fixed. I wonder why we don't have a bug open for util-linux to track this further. (In reply to Joonas Niilola from comment #8) > I wonder why we don't have a bug open for util-linux to track this further. I wonder too ;) I could not find one for util-linux, but figured there's no way some tinderbox run tested out loop-aes-losetup before testing util-linux, so maybe my bugzilla foo is lacking, or, the tinderbox tests were against some local branch of ::gentoo that's not merged yet, that already contains util-linux fixes. At the same time, I'm not sure my local reproduction of "CC=clang breaks util-linux" is done "correctly", so would rather not create such a bug myself in case it's just noise. This is fixed in the bump I submitted a few weeks ago, https://github.com/gentoo/gentoo/pull/34121 It is just awaiting someone with ::gentoo commit access to merge. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=82d17ecf3c2a5544c4a29a75702f403251bbdd58 commit 82d17ecf3c2a5544c4a29a75702f403251bbdd58 Author: Hank Leininger <hlein@korelogic.com> AuthorDate: 2023-12-03 23:43:34 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2024-02-01 08:28:17 +0000 app-crypt/loop-aes-losetup: add 2.39.2 Signed-off-by: Hank Leininger <hlein@korelogic.com> Closes: https://bugs.gentoo.org/870745 Closes: https://github.com/gentoo/gentoo/pull/34121 Signed-off-by: Joonas Niilola <juippis@gentoo.org> app-crypt/loop-aes-losetup/Manifest | 2 + .../loop-aes-losetup-2.39.2.ebuild | 71 ++++++++++++++++++++++ 2 files changed, 73 insertions(+) |