WireGuard Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [WireGuard] Error building against grsec-enabled kernel
Date: Wed, 19 Oct 2016 15:03:48 +0200	[thread overview]
Message-ID: <87mvi0jxsb.fsf@toke.dk> (raw)

I'm getting build errors when building WireGuard against a grsec-enabled
kernel (on Arch linux):

DKMS make.log for wireguard-0.0.20161014 for kernel 4.7.8.201610161720-1-gr=
sec (x86_64)
Wed 19 Oct 14:59:25 CEST 2016
make: Entering directory '/usr/lib/modules/4.7.8.201610161720-1-grsec/build'
  LD      /var/lib/dkms/wireguard/0.0.20161014/build/built-in.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20161014/build/main.o
/var/lib/dkms/wireguard/0.0.20161014/build/main.o: warning: objtool: mod_ex=
it(): can't find starting instruction
  CC [M]  /var/lib/dkms/wireguard/0.0.20161014/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/0.0.20161014/build/device.o
/var/lib/dkms/wireguard/0.0.20161014/build/device.c:330:29: error: constifi=
ed variable =E2=80=98link_ops=E2=80=99 placed into writable section ".data.=
.read_mostly"
 static struct rtnl_link_ops link_ops __read_mostly =3D {
                             ^~~~~~~~
make[1]: *** [scripts/Makefile.build:290: /var/lib/dkms/wireguard/0.0.20161=
014/build/device.o] Error 1
make: *** [Makefile:1465: _module_/var/lib/dkms/wireguard/0.0.20161014/buil=
d] Error 2
make: Leaving directory '/usr/lib/modules/4.7.8.201610161720-1-grsec/build'


Any idea how to fix this?

-Toke

             reply	other threads:[~2016-10-19 13:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 13:03 Toke Høiland-Jørgensen [this message]
2016-10-19 14:18 ` [WireGuard] Error building against grsec-enabled kernel Toke Høiland-Jørgensen
2016-10-19 16:07   ` Toke Høiland-Jørgensen
2016-10-19 22:35     ` Jason A. Donenfeld
2016-10-20  2:19     ` Jason A. Donenfeld
2016-10-21  0:24       ` PaX Team
2016-10-21  2:32         ` Jason A. Donenfeld
2016-10-21  8:02           ` PaX Team
2016-10-21  8:47             ` Jason A. Donenfeld
2016-10-21  9:46               ` PaX Team
2016-10-22  7:56                 ` Jason A. Donenfeld
2016-10-21  9:53               ` Toke Høiland-Jørgensen
2016-10-22  8:03                 ` Jason A. Donenfeld
2016-10-22 13:10                   ` Toke Høiland-Jørgensen
2016-10-23 10:23                     ` Jason A. Donenfeld

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=87mvi0jxsb.fsf@toke.dk \
    --to=toke@toke.dk \
    --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