From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/3] network-manager: bump version to 1.8.0
Date: Thu, 11 May 2017 21:18:44 +0200 [thread overview]
Message-ID: <20170511211844.62d2f695@free-electrons.com> (raw)
In-Reply-To: <20170511135639.43280-1-Vincent.Riera@imgtec.com>
Hello,
On Thu, 11 May 2017 14:56:37 +0100, Vicente Olivert Riera wrote:
> Added --disable-concheck to avoid configure failure when libcurl is not
> available:
>
> checking for LIBCURL... no
> configure: error: --enable-concheck requires libcurl library.
>
> One would expect the concheck functionality to be automatically disabled
> if libcurl is not found. But upstream wants to be explicitly disabled if
> now wanted to prevent building NetworkManager without connectivity
> check support without any evident warning on systems where libcurl is
> not installed. See:
>
> https://github.com/NetworkManager/NetworkManager/commit/faa1b85dab647baad7ce856e83f343af841aa6a5
>
> Proper support for concheck will be added in a subsequent patch.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/network-manager/network-manager.hash | 4 ++--
> package/network-manager/network-manager.mk | 7 ++++---
> 2 files changed, 6 insertions(+), 5 deletions(-)
Series applied to next, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-11 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 13:56 [Buildroot] [PATCH next 1/3] network-manager: bump version to 1.8.0 Vicente Olivert Riera
2017-05-11 13:56 ` [Buildroot] [PATCH next 2/3] network-manager: add optional concheck support Vicente Olivert Riera
2017-05-11 13:56 ` [Buildroot] [PATCH next 3/3] network-manager: add optional ofono support Vicente Olivert Riera
2017-05-11 19:18 ` Thomas Petazzoni [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=20170511211844.62d2f695@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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