From: Michael <gravitygrazer@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: RHEL8 package install or build fail
Date: Wed, 26 Jun 2019 15:18:59 +0200 [thread overview]
Message-ID: <CADXv92b2P79-OJBzK+aXhKFr3k_VqZkkkAuZOg5dALui8aNTiA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1249 bytes --]
folks, current wireguard seems not to install or build on RHEL 8.0
(1) via yum and the wireguard repo at
https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard/epel-7-$basearch/
[root@<>]# yum install wireguard-dkms wireguard-tools
...
Copr repo for wireguard owned by jdoss
1.7 kB/s | 3.5 kB 00:01
Error:
Problem 1: conflicting requests
- nothing provides dkms needed by
wireguard-dkms-1:0.0.20190601-1.el7.noarch
Problem 2: package wireguard-tools-1:0.0.20190601-1.el7.x86_64 requires
wireguard-dkms, but none of the providers can be installed
and (2) building without much trying albeit -
[root@<> src]# make
CC [M] /root/WireGuard/src/main.o
In file included from <command-line>:
/root/WireGuard/src/compat/compat.h:828:20: error: redefinition of
'skb_mark_not_on_list'
static inline void skb_mark_not_on_list(struct sk_buff *skb)
^~~~~~~~~~~~~~~~~~~~
In file included from /root/WireGuard/src/compat/compat.h:787,
from <command-line>:
./include/linux/skbuff.h:1362:20: note: previous definition of
'skb_mark_not_on_list' was here
static inline void skb_mark_not_on_list(struct sk_buff *skb)
^~~~~~~~~~~~~~~~~~~~
Thanks in advance for hints,
-- Mike
[-- Attachment #1.2: Type: text/html, Size: 1744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-06-28 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:18 Michael [this message]
2019-06-28 12:03 ` Jason A. Donenfeld
2019-06-28 12:05 ` Christopher Bachner
2019-06-28 12:07 ` Jason A. Donenfeld
2019-06-28 12:32 ` Jason A. Donenfeld
2019-06-28 14:41 ` Michael
2019-06-28 14:52 ` Jason A. Donenfeld
2019-07-02 19:51 ` Joe Doss
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=CADXv92b2P79-OJBzK+aXhKFr3k_VqZkkkAuZOg5dALui8aNTiA@mail.gmail.com \
--to=gravitygrazer@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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).