From: Vadym Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/keepalived: make suport for Linux headers >= 3.2
Date: Fri, 16 Oct 2020 15:22:40 +0300 [thread overview]
Message-ID: <20201016122240.4235-1-vadim4j@gmail.com> (raw)
From: Vadym Kochan <vadym.kochan@plvision.eu>
There are some toolchains which is compiled with Linux 3.2 heaers, it
would good to support them too because the package bulds fine with them.
Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
---
package/keepalived/Config.in | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/keepalived/Config.in b/package/keepalived/Config.in
index c71821545c..223ed5a4e6 100644
--- a/package/keepalived/Config.in
+++ b/package/keepalived/Config.in
@@ -2,7 +2,7 @@ config BR2_PACKAGE_KEEPALIVED
bool "keepalived"
depends on BR2_USE_MMU
depends on !BR2_STATIC_LIBS # uses libdl
- depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4
+ depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
select BR2_PACKAGE_OPENSSL
help
The main goal of the keepalived project is to add a strong &
@@ -15,6 +15,6 @@ config BR2_PACKAGE_KEEPALIVED
http://www.keepalived.org/
-comment "keepalived needs a toolchain w/ dynamic library, headers >= 3.4"
+comment "keepalived needs a toolchain w/ dynamic library, headers >= 3.2"
depends on BR2_USE_MMU
- depends on BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4
+ depends on BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
--
2.17.1
next reply other threads:[~2020-10-16 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 12:22 Vadym Kochan [this message]
2020-10-16 12:27 ` [Buildroot] [PATCH] package/keepalived: make suport for Linux headers >= 3.2 Thomas Petazzoni
[not found] ` <20201016135120.GA4852@plvision.eu>
2020-10-16 18:07 ` Thomas Petazzoni
2020-10-25 9:25 ` Thomas Petazzoni
2020-10-25 18:01 ` Vadym Kochan
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=20201016122240.4235-1-vadim4j@gmail.com \
--to=vadim4j@gmail.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