Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17
Date: Thu, 19 Jul 2018 09:20:38 +0200	[thread overview]
Message-ID: <20180719092038.3aac3f6a@windsurf> (raw)
In-Reply-To: <20180718201855.GC21354@australia>

Hello,

On Wed, 18 Jul 2018 22:18:55 +0200, Thomas De Schampheleire wrote:

> Problem here is the configuration of libssh2 with a non-openssl backend, which I
> had not tested.

So libssh2 doesn't fully "abstract" the specific crypto backend being
used ?

> The log seems to offer a suggestion on how to allow gcrypt as backend, which I
> have yet to try. And for mbedtls there is no suggestion, so likely not
> supported.
> 
> I need some more time to investigate this and propose a fix. Personally I'm only
> interested in the openssl backend, so another approach is to restrict it to
> that.

I'm fine with that approach.

> In that case I wonder how to achieve it: should I select both LIBSSH2 and
> LIBSSH2_OPENSSL and OPENSSL itself?

You can't select LIBSSH2_OPENSSL, because it is part of a choice. I'm
afraid you don't have any other solution but to "depends on
BR2_PACKAGE_LIBSSH2_OPENSSL". It is not ideal because it's clearly not
obvious for the user, but well.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-07-19  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180718060040.E770E208FF@mail.bootlin.com>
2018-07-18 20:18 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17 Thomas De Schampheleire
2018-07-19  7:20   ` 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=20180719092038.3aac3f6a@windsurf \
    --to=thomas.petazzoni@bootlin.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