Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Christopher Ng <facboy@gmail.com>
To: Joe Doss <joe@solidadmin.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard not available for CentOS Stream
Date: Tue, 12 Jan 2021 09:57:27 +0000	[thread overview]
Message-ID: <CAN5wt5rqnPXwD5FdvoocxaXPvDOb_O2Fj_aBq98EKCc2R5JA1Q@mail.gmail.com> (raw)
In-Reply-To: <176cafeade8.27b6.fd5e59abeac6319e4fe4e8192ea7d08d@solidadmin.com>

dkms doesn't work on CentOSStream at the moment:

DKMS make.log for wireguard-1.0.20201221 for kernel
4.18.0-259.el8.x86_64 (x86_64)
Tue 12 Jan 09:55:51 GMT 2021
make: Entering directory '/usr/src/kernels/4.18.0-259.el8.x86_64'
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/main.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/device.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/peer.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/send.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/receive.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/socket.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/peerlookup.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/allowedips.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/ratelimiter.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/cookie.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/netlink.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/chacha20/chacha20.o
  PERLASM /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/chacha20/chacha20-x86_64.S
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/poly1305/poly1305.o
  PERLASM /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/poly1305/poly1305-x86_64.S
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/chacha20poly1305.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s.o
  AS [M]  /var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.o
In file included from <command-line>:
/var/lib/dkms/wireguard/1.0.20201221/build/compat/compat-asm.h:44:
warning: "SYM_FUNC_START" redefined
 #define SYM_FUNC_START ENTRY

In file included from
/var/lib/dkms/wireguard/1.0.20201221/build/compat/compat-asm.h:9,
                 from <command-line>:
./include/linux/linkage.h:218: note: this is the location of the
previous definition
 #define SYM_FUNC_START(name)    \

In file included from <command-line>:
/var/lib/dkms/wireguard/1.0.20201221/build/compat/compat-asm.h:45:
warning: "SYM_FUNC_END" redefined
 #define SYM_FUNC_END ENDPROC

In file included from
/var/lib/dkms/wireguard/1.0.20201221/build/compat/compat-asm.h:9,
                 from <command-line>:
./include/linux/linkage.h:265: note: this is the location of the
previous definition
 #define SYM_FUNC_END(name)    \

/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.S:
Assembler messages:
/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.S:50:
Error: invalid character '(' in mnemonic
/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.S:176:
Error: invalid character '(' in mnemonic
/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.S:180:
Error: invalid character '(' in mnemonic
/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.S:257:
Error: invalid character '(' in mnemonic
make[1]: *** [scripts/Makefile.build:415:
/var/lib/dkms/wireguard/1.0.20201221/build/crypto/zinc/blake2s/blake2s-x86_64.o]
Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1545:
_module_/var/lib/dkms/wireguard/1.0.20201221/build] Error 2
make: Leaving directory '/usr/src/kernels/4.18.0-259.el8.x86_64'

On Mon, 4 Jan 2021 at 01:26, Joe Doss <joe@solidadmin.com> wrote:
>
> https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/
>
> The official DKMS install method for CentOS has a Stream repo enabled. It
> should work fine. Let us know if you have any issues.
>
> Joe
>
> On January 3, 2021 2:19:30 PM Silvan Nagl <mail@53c70r.de> wrote:
>
> > Hi,
> >
> > i noticed that no Wireguard installation source currently supports
> > CentOS Stream and its newer Kernels.
> > Will there be support for it?
> >
> > Greetings,
> >
> > Silvan
>
>
>

      parent reply	other threads:[~2021-01-12 10:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 20:17 Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04  1:24 ` Joe Doss
2021-01-04 12:47   ` Jason A. Donenfeld
     [not found]     ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42       ` Joe Doss
2021-01-04 20:25         ` Bruno Wolff III
2021-01-04 21:55     ` Jeffrey Walton
2021-01-05 11:25       ` Jonathan Aquilina
2021-01-05 18:35         ` Joe Doss
2021-01-05 18:14       ` Joe Doss
     [not found]       ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06  9:32         ` Silvan Nagl
     [not found]     ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06       ` Silvan Nagl
2021-01-05 13:56         ` Jeffrey Walton
2021-01-05 14:58           ` Toke Høiland-Jørgensen
2021-01-12  9:57   ` Christopher Ng [this message]

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=CAN5wt5rqnPXwD5FdvoocxaXPvDOb_O2Fj_aBq98EKCc2R5JA1Q@mail.gmail.com \
    --to=facboy@gmail.com \
    --cc=joe@solidadmin.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).