From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: problems with zfs-0.8.3_2
Date: Sun, 05 Apr 2020 23:26:59 +0200 [thread overview]
Message-ID: <20200405212659.mkQXUmXabQ0RHF22kkOhCnZMnVemauU04IcH4sbzEpo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20673@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/20673#issuecomment-609486705
Comment:
The `zfs-0.8.3_2` DKMS builds for me with `linux4.14-414.174_1` on x86_64. Your text references `linux4.14`, but your output refers to `linux4.19`. I've had no problems building against either. Can you reconcile the difference and see if there is a DKMS build log in `/var/lib/dkms/zfs/0.8.3/build/make.log` that explains the error?
next prev parent reply other threads:[~2020-04-05 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 16:02 [ISSUE] " emacsomancer
2020-04-05 16:04 ` xtraeme
2020-04-05 16:09 ` emacsomancer
2020-04-05 16:09 ` emacsomancer
2020-04-05 16:09 ` emacsomancer
2020-04-05 21:26 ` ahesford [this message]
2020-04-05 22:09 ` ahesford
2020-04-06 2:13 ` emacsomancer
2020-04-06 2:13 ` [ISSUE] [CLOSED] " emacsomancer
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=20200405212659.mkQXUmXabQ0RHF22kkOhCnZMnVemauU04IcH4sbzEpo@z \
--to=ahesford@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).