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: Sun, 30 Jul 2023 23:22:26 +0200 [thread overview]
Message-ID: <20230730212226.gTC-s49jjJ1r0WJIIv0n-EOlaVfMdpU0Krq5Uq-GYTw@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: 1084 bytes --]
New comment by r-ricci on void-packages repository
https://github.com/void-linux/void-packages/issues/44807#issuecomment-1657269573
Comment:
I built natively the package linux6.3 on aarch64-musl. I don't get the error related to powerpc files anymore, so it's probably something related to cross-compilation.
I still can't build zfs, but I think this is an unrelated problem:
```
MODPOST /var/lib/dkms/zfs/2.1.12/build/module/Module.symvers
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_begin'
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin'
make[2]: *** [scripts/Makefile.modpost:136: /var/lib/dkms/zfs/2.1.12/build/module/Module.symvers] Error 1
make[1]: *** [Makefile:1977: modpost] Error 2
make: *** [Makefile:55: modules-Linux] Error 2
make: Leaving directory '/var/lib/dkms/zfs/2.1.12/build/module'
```
next prev parent reply other threads:[~2023-07-30 21:22 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 [this message]
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=20230730212226.gTC-s49jjJ1r0WJIIv0n-EOlaVfMdpU0Krq5Uq-GYTw@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).