From: egrain <egrain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs on musl: Building DKMS module 'zfs-2.1.9' for kernel-6.1.19_1... FAILED!
Date: Mon, 20 Mar 2023 16:18:35 +0100 [thread overview]
Message-ID: <20230320151835.e4LyLVU_kOZqwpmScmAXKyYwQJk_d5rfqlaLQux2hL0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42871@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
New comment by egrain on void-packages repository
https://github.com/void-linux/void-packages/issues/42871#issuecomment-1476413358
Comment:
$ xbps-query -p pkgver zfs; xbps-query -p pkgver linux6.1; xbps-query -p pkgver linux6.1-headers
zfs-2.1.9_1
linux6.1-6.1.19_1
linux6.1-headers-6.1.19_1
$ uname -a | sed -E 's/^Linux\s(\S+)/musl/g'
I saw the dependencies of xtools, and figured only musl was missing, so I replaced the first two words with it.
$ xbps-query -Rs musl |grep \\*
[\*] musl-1.1.24_15 Musl C library
[\*] musl-fts-1.2.7_4 Implementation of fts(3) for musl libc
Ha, this one is better, I think:
$ xbps-query -l|grep musl
ii musl-1.1.24_15 Musl C library
ii musl-devel-1.1.24_15 Musl C library - development files
ii musl-fts-1.2.7_4 Implementation of fts(3) for musl libc
Oh, sshed into the wrong box. anyway, i have the devel file installed on the newer box where the other stuff is from. Sorry for the confusion.
next prev parent reply other threads:[~2023-03-20 15:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 21:00 [ISSUE] " egrain
2023-03-20 2:32 ` sgn
2023-03-20 8:02 ` egrain
2023-03-20 10:02 ` egrain
2023-03-20 14:43 ` sgn
2023-03-20 14:47 ` sgn
2023-03-20 15:11 ` egrain
2023-03-20 15:12 ` egrain
2023-03-20 15:16 ` egrain
2023-03-20 15:18 ` egrain [this message]
2023-03-20 16:01 ` sgn
2023-03-20 16:11 ` egrain
2023-03-20 16:21 ` sgn
2023-03-20 16:26 ` sgn
2023-03-20 16:40 ` egrain
2023-03-20 16:46 ` sgn
2023-03-20 16:47 ` sgn
2023-03-20 16:47 ` egrain
2023-03-20 16:50 ` sgn
2023-03-20 16:52 ` egrain
2023-03-20 17:05 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:14 ` egrain
2023-03-20 17:16 ` paper42
2023-03-20 17:17 ` paper42
2023-03-20 17:27 ` egrain
2023-03-21 0:44 ` sgn
2023-03-21 9:13 ` egrain
2023-03-21 10:39 ` [ISSUE] [CLOSED] " paper42
2023-03-23 1:59 ` sgn
2023-03-23 7:45 ` egrain
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=20230320151835.e4LyLVU_kOZqwpmScmAXKyYwQJk_d5rfqlaLQux2hL0@z \
--to=egrain@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).