From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] DKMS Modules Fail to Build on aarch64 - Missing powerpc Headers
Date: Sun, 01 Oct 2023 22:21:09 +0200 [thread overview]
Message-ID: <20231001202109.9012LL5lZOeM9EghHFH9nTwh6-NXz7FXiW3Alksfa-Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44807@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Closed issue by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/issues/44807
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.10_1 aarch64-musl Unknown uptodate rFF
### Package(s) Affected
linux-headers-6.3_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
installing a package that includes a DKMS module (eg. zfs, wireguard) builds the module successfully
### Actual behaviour
DKMS Module fails to build. Log files mention missing "arch/powerpc/crypto/Kconfig"
### Steps to reproduce
1. xbps-install zfs
2. Error
prev parent reply other threads:[~2023-10-01 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 2:57 [ISSUE] " Calandracas606
2023-07-03 3:05 ` Calandracas606
2023-07-03 3:07 ` Calandracas606
2023-07-03 3:07 ` Calandracas606
2023-07-04 15:45 ` abenson
2023-07-30 21:22 ` r-ricci
2023-08-01 23:38 ` r-ricci
2023-08-16 21:17 ` r-ricci
2023-09-17 21:21 ` moabeat-berlin
2023-09-29 22:01 ` classabbyamp
2023-09-30 6:44 ` Calandracas606
2023-09-30 6:45 ` Calandracas606
2023-10-01 20:21 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231001202109.9012LL5lZOeM9EghHFH9nTwh6-NXz7FXiW3Alksfa-Q@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).