From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17
Date: Wed, 18 Jul 2018 22:18:55 +0200 [thread overview]
Message-ID: <20180718201855.GC21354@australia> (raw)
In-Reply-To: <20180718060040.E770E208FF@mail.bootlin.com>
Hi,
On Wed, Jul 18, 2018 at 08:00:40AM +0200, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2018-07-17, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Results for the 'master' branch
> ===============================
>
> Build failures related to your packages:
>
> mipsel | perl-net-ssh2-0.69 | http://autobuild.buildroot.net/results/6ee18e7dd17f168c52f79e49cb5e94cf3aa3df1a
>
Problem here is the configuration of libssh2 with a non-openssl backend, which I
had not tested.
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.
In that case I wonder how to achieve it: should I select both LIBSSH2 and
LIBSSH2_OPENSSL and OPENSSL itself?
Or should I make the entire perl-net-ssh2 depend on openssl and libssh2_openssl
before making it visible?
Thanks,
Thomas
next parent reply other threads:[~2018-07-18 20:18 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 ` Thomas De Schampheleire [this message]
2018-07-19 7:20 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17 Thomas Petazzoni
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=20180718201855.GC21354@australia \
--to=thomas.de_schampheleire@nokia.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