[Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17

[Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17

[Thomas De Schampheleire]

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

[Buildroot] [autobuild.buildroot.net] Your build results for 2018-07-17

[Thomas Petazzoni]

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