From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libssh2: fix build with libgcrypt and mbedtls enabled
Date: Sat, 29 Jul 2017 15:52:42 +0200 [thread overview]
Message-ID: <20170729155242.3a67c438@windsurf.lan> (raw)
In-Reply-To: <aee7e0b01fec4b43854973bba5a967f438d6dcb4.1501216093.git.baruch@tkos.co.il>
Hello,
On Fri, 28 Jul 2017 07:28:13 +0300, Baruch Siach wrote:
> The --without-libgcrypt configure parameter is not enough to disable the
> libgcrypt back-end. This breaks the build when mbedtls (default backend) is
> enabled, and libgcrypt builds before libssh2. Seed ac_cv_libgcrypt to really
> disable libgcrypt when it is not the selected crypto back-end.
>
> Fixes:
> http://autobuild.buildroot.net/results/b4e/b4e39890e003e9e590a5bf17c9300c653020d88c/
> http://autobuild.buildroot.net/results/45a/45a9b3559ceea4e1399794f9612f717f7c57a4a3/
> http://autobuild.buildroot.net/results/ae4/ae4afec62ca297df1cd02350601f1d62fc3cd1b7/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/libssh2/libssh2.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks. However, could you submit a bug report
upstream, because this is clearly a bug.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-29 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 4:28 [Buildroot] [PATCH] libssh2: fix build with libgcrypt and mbedtls enabled Baruch Siach
2017-07-29 13:52 ` Thomas Petazzoni [this message]
2017-07-29 18:31 ` Baruch Siach
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=20170729155242.3a67c438@windsurf.lan \
--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