Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireguard: needs 3.10+ kernel
Date: Tue,  3 Oct 2017 10:04:48 +0200	[thread overview]
Message-ID: <20171003080448.3809-1-peter@korsgaard.com> (raw)

The dependency is actually only for the kernel module (and thus on the
runtime kernel version rather than kernel headers), but as we don't know the
runtime version in kconfig this will have to do.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 package/wireguard/Config.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/package/wireguard/Config.in b/package/wireguard/Config.in
index 0321755db3..acce6663ba 100644
--- a/package/wireguard/Config.in
+++ b/package/wireguard/Config.in
@@ -1,5 +1,6 @@
 config BR2_PACKAGE_WIREGUARD
 	bool "wireguard"
+	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
 	select BR2_PACKAGE_LIBMNL
 	help
 	  WireGuard is an extremely simple yet fast and modern VPN
@@ -16,3 +17,6 @@ config BR2_PACKAGE_WIREGUARD
 	  VPN solution in the industry.
 
 	  https://www.wireguard.com
+
+comment "wireguard needs a toolchain w/ headers > 3.10"
+	depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
-- 
2.11.0

             reply	other threads:[~2017-10-03  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  8:04 Peter Korsgaard [this message]
2017-10-05 18:44 ` [Buildroot] [PATCH] wireguard: needs 3.10+ kernel Arnout Vandecappelle
2017-10-05 19:46   ` Peter Korsgaard
2017-10-05 19:51     ` Arnout Vandecappelle
2017-10-05 20:53       ` Peter Korsgaard

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=20171003080448.3809-1-peter@korsgaard.com \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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