From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/sngrep: add libgcrypt missing dependencies
Date: Tue, 23 May 2017 16:19:50 +0200 [thread overview]
Message-ID: <20170523161950.2b24f43f@free-electrons.com> (raw)
In-Reply-To: <20170520162751.30809-1-romain.naour@gmail.com>
Hello,
On Sat, 20 May 2017 18:27:50 +0200, Romain Naour wrote:
> Even if libgcrypt is selected at Kconfig level, it's missing from
> Makefile level.
>
> Fixes:
> http://autobuild.buildroot.net/results/36c/36c28e7e49b31ed2398a67db2e9b08e3aad5a3ee
Could you explain how this build failure apparently related to ncurses
has something to do with the gnutls/libgcrypt issue ?
The patch itself looks good, but the relation with this particular
build failure isn't really clear. Could you clarify?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-23 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 16:27 [Buildroot] [PATCH 1/2] package/sngrep: add libgcrypt missing dependencies Romain Naour
2017-05-20 16:27 ` [Buildroot] [PATCH 2/2] package/sngrep: fix static build with gnutls Romain Naour
2017-05-23 14:27 ` Thomas Petazzoni
2017-05-23 21:20 ` Romain Naour
2017-05-24 6:47 ` Thomas Petazzoni
2017-05-24 21:54 ` Romain Naour
2017-05-25 9:02 ` Bernd Kuhls
2017-05-25 16:32 ` Romain Naour
2017-05-23 14:19 ` Thomas Petazzoni [this message]
2017-05-23 21:09 ` [Buildroot] [PATCH 1/2] package/sngrep: add libgcrypt missing dependencies Romain Naour
2017-05-24 6:44 ` Thomas Petazzoni
2017-05-24 19:41 ` Romain Naour
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=20170523161950.2b24f43f@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