From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] Zfs 0.8.0
Date: Tue, 11 Jun 2019 01:29:50 +0200 [thread overview]
Message-ID: <20190610232950.euyCm196VN-kuQmM4jW-bSn9eJkkV03eqKn9n59wt3I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11994@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]
New comment by kapcom01 on void-packages repository
https://github.com/void-linux/void-packages/pull/11994#issuecomment-500630112
Comment:
Hello. I have a Raspberry Pi 3 with the _void-rpi2-PLATFORMFS-20181111_ image installed.
The package was built successfully following the [guide on the wiki](https://wiki.voidlinux.org/Xbps-src#Quick_Start) but when I tried to install it with `xi zfs` it failed to build dkms just like zfs 0.7.13.
```
# xi zfs
....
....
zfs-0.8.0_1: configuring ...
Added DKMS module 'zfs-0.8.0'.
Skipping kernel-4.14.79_1. kernel-headers package not installed...
Building DKMS module 'zfs-0.8.0' for kernel-4.19.46_1... FAILED!
DKMS module 'zfs-0.8.0' failed to build, please check /var/lib/dkms
for errors in the log file.
Building DKMS module 'zfs-0.8.0' for kernel-4.19.49_1... FAILED!
DKMS module 'zfs-0.8.0' failed to build, please check /var/lib/dkms
for errors in the log file.
zfs-0.8.0_1: installed successfully.
0 downloaded, 26 installed, 0 updated, 26 configured, 0 removed.
```
Here is the build log: [/var/lib/dkms/zfs/0.8.0/build/config.log](https://github.com/void-linux/void-packages/files/3274126/config.log)
Then I tried to build the missing plugins:
```
# cd /usr/src/rpi-kernel-headers-4.19.46_1/
# make scripts
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --syncconfig Kconfig
drivers/ras/Kconfig:33: can't open file "arch/x86/ras/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:69: syncconfig] Error 1
make[1]: *** [Makefile:539: syncconfig] Error 2
make: *** [Makefile:638: include/config/auto.conf.cmd] Error 2
make: *** [include/config/auto.conf.cmd] Deleting file 'include/config/tristate.conf'
```
next prev parent reply other threads:[~2019-06-10 23:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11994@inbox.vuxu.org>
2019-06-05 13:58 ` voidlinux-github
2019-06-05 14:07 ` voidlinux-github
2019-06-05 18:28 ` voidlinux-github
2019-06-05 18:56 ` voidlinux-github
2019-06-05 19:22 ` voidlinux-github
2019-06-05 19:44 ` voidlinux-github
2019-06-05 19:48 ` voidlinux-github
2019-06-05 19:49 ` voidlinux-github
2019-06-05 19:51 ` voidlinux-github
2019-06-05 19:54 ` voidlinux-github
2019-06-05 21:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-05 21:31 ` voidlinux-github
2019-06-05 21:33 ` voidlinux-github
2019-06-07 4:20 ` voidlinux-github
2019-06-07 17:56 ` voidlinux-github
2019-06-08 18:41 ` voidlinux-github
2019-06-08 18:42 ` voidlinux-github
2019-06-10 23:29 ` voidlinux-github [this message]
2019-06-10 23:37 ` voidlinux-github
2019-06-11 9:42 ` voidlinux-github
2019-06-11 12:23 ` voidlinux-github
2019-06-12 6:09 ` voidlinux-github
2019-06-12 12:55 ` voidlinux-github
2019-06-12 16:47 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190610232950.euyCm196VN-kuQmM4jW-bSn9eJkkV03eqKn9n59wt3I@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).