From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: DKMS Modules Fail to Build on aarch64 - Missing powerpc Headers
Date: Mon, 03 Jul 2023 05:07:09 +0200 [thread overview]
Message-ID: <20230703030709.XBN3QU-GmAOcgC7efGV08z62DccAJFissmeaOLQ1uoQ@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: 5457 bytes --]
New comment by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/issues/44807#issuecomment-1617154054
Comment:
example when installing zfs (similar errors with other DKMS modules such as Wireguard)
```
Added DKMS modules 'zfs-2.1.12'.
Prepare to build modules for kernel-6.3.10_1... FAILED!
Kernel scripts failed to build, please check /lib/modules/6.3.10_1/build/make.log
for errors in the log file.
Building DKMS module 'zfs-2.1.12' for kernel-6.3.10_1... FAILED!
DKMS module 'zfs-2.1.12' failed to build, please check /var/lib/dkms
for errors in the log file.
Regenerating initramfs images using kernel hook 20-initramfs
dracut-install: Failed to find module 'zfs'
dracut: FAILED: /usr/lib/dracut/dracutinstall -D /var/tmp/dracut.pDCU9N/initramfs --kerneldir /lib/modules/6.3.10_1/ -m zfs
dracut: installkernel failed in module zfs
zfs-2.1.12_1: installed successfully.
```
contents of /lib/modules/6.3.10_1/build/make.log
```
make: Entering directory '/usr/src/kernel-headers-6.3.10_1'
SYNC include/config/auto.conf.cmd
crypto/Kconfig:1402: can't open file "arch/powerpc/crypto/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: syncconfig] Error 1
make[1]: *** [Makefile:693: syncconfig] Error 2
make: *** [Makefile:793: include/config/auto.conf.cmd] Error 2
make: Leaving directory '/usr/src/kernel-headers-6.3.10_1'
```
contents of /var/lib/dkms/zfs/2.1.12/build/make.log
```
DKMS make.log for zfs-2.1.12 for kernel 6.3.10_1 (aarch64)
Mon Jul 3 00:00:53 EDT 2023
make: Entering directory '/var/lib/dkms/zfs/2.1.12/build/module'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory '/var/lib/dkms/zfs/2.1.12/build/module'
```
next prev parent reply other threads:[~2023-07-03 3:07 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 [this message]
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 ` [ISSUE] [CLOSED] " classabbyamp
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=20230703030709.XBN3QU-GmAOcgC7efGV08z62DccAJFissmeaOLQ1uoQ@z \
--to=calandracas606@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).