From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: DKMS Modules Fail to Build on aarch64 - Missing powerpc Headers
Date: Wed, 02 Aug 2023 01:38:55 +0200 [thread overview]
Message-ID: <20230801233855.nIe0Gf9qnIZpGc5hXpJjPZpSkgg0XJKkxTOWWIQ_f3E@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: 1052 bytes --]
New comment by r-ricci on void-packages repository
https://github.com/void-linux/void-packages/issues/44807#issuecomment-1661246227
Comment:
Actually the problem does not seem to be cross-compilation. This issue doesn't affect the natively built kernel package just because this one doesn't require the helper tools to be rebuilt.
If I make these changes:
```diff
--- /etc/kernel.d/post-install/10-dkms.old
+++ /etc/kernel.d/post-install/10-dkms
@@ -19,9 +19,7 @@
export IGNORE_CC_MISMATCH=1
-if [ ! -f /lib/modules/${VERSION}/build/scripts/basic/fixdep ] || [ ! -f /lib/modules/${VERSION}/build/scripts/mod/modpost ]; then
yes "" | make -j $(nproc) -C /lib/modules/${VERSION}/build prepare0
-fi
# Check available DKMS modules
for _mod_ in /var/lib/dkms/*; do
```
then `xbps-reconfigure -f linux6.3` fails with the error mentioned by @Calandracas606, both with a cross-compiled kernel and a native one.
I tried the same thing on a x86_64 system and it fails too (even though the missing files are not the same).
next prev parent reply other threads:[~2023-08-01 23:38 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 [this message]
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=20230801233855.nIe0Gf9qnIZpGc5hXpJjPZpSkgg0XJKkxTOWWIQ_f3E@z \
--to=r-ricci@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).