All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libssh: needs libopenssl for openssl crypto Backend
Date: Sun, 11 Oct 2026 15:49:35 +0200	[thread overview]
Message-ID: <asuTyI8vN5fjihif@windsurf> (raw)
In-Reply-To: <20260809095505.508811-1-bernd@kuhls.net>

On Sun, Aug 09, 2026 at 11:55:05AM +0200, Bernd Kuhls wrote:
> diff --git a/package/libssh/Config.in b/package/libssh/Config.in
> index eaec754414..9aa2bfaf86 100644
> --- a/package/libssh/Config.in
> +++ b/package/libssh/Config.in
> @@ -35,7 +35,7 @@ config BR2_PACKAGE_LIBSSH_LIBGCRYPT
>  
>  config BR2_PACKAGE_LIBSSH_OPENSSL
>  	bool "openssl"
> -	depends on BR2_PACKAGE_OPENSSL
> +	depends on BR2_PACKAGE_LIBOPENSSL
>  	select BR2_PACKAGE_LIBOPENSSL_ENGINES

Thanks a lot, but this was not the proper fix. The proper fix was
instead:

  https://gitlab.com/buildroot.org/buildroot/-/commit/f7fe354adadac3d2425fbe59da0744f1e4103726

so that libressl can still be used.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-13 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09  9:55 [Buildroot] [PATCH 1/1] package/libssh: needs libopenssl for openssl crypto Backend Bernd Kuhls
2026-10-11 13:49 ` Thomas Petazzoni via buildroot [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=asuTyI8vN5fjihif@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.