From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/sngrep: add libgcrypt missing dependencies
Date: Wed, 24 May 2017 08:44:39 +0200 [thread overview]
Message-ID: <20170524084439.56e64c59@free-electrons.com> (raw)
In-Reply-To: <f09dc6c1-557c-885b-4bb9-370a1ca9b8ae@gmail.com>
Hello,
On Tue, 23 May 2017 23:09:19 +0200, Romain Naour wrote:
> I was looking for this kind of build failure with a glibc based system:
>
> checking for ncurses.h... yes
> checking for initscr in -lncurses... yes
> checking for new_panel in -lpanel... yes
> checking for new_form in -lform... yes
> checking for new_item in -lmenu... yes
> checking for gnutls_init in -lgnutls... yes
> checking for gcry_md_map_name in -lgcrypt... no
> configure: error: You need to have libgcrypt installed to compile sngrep
>
> I just read what I wanted to read in the autobuilder reference...
>
> It's weird that the autobuilder didn't catch it.
So in other words, there are no autobuilder reference for the build
failure you are fixing? If so, could you add in the commit log a
minimal defconfig that exhibits the issue?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-24 6:44 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 ` [Buildroot] [PATCH 1/2] package/sngrep: add libgcrypt missing dependencies Thomas Petazzoni
2017-05-23 21:09 ` Romain Naour
2017-05-24 6:44 ` Thomas Petazzoni [this message]
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=20170524084439.56e64c59@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