All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libssh: select BR2_PACKAGE_LIBOPENSSL_ENGINES
Date: Tue, 16 Jul 2024 12:40:07 +0200	[thread overview]
Message-ID: <02e5180ddafe94a9a3d48fdb1dcc8cc2221abeb8.camel@gmail.com> (raw)
In-Reply-To: <878qy14rqg.fsf@tarshish>

Hi Baruch,

On Tue, 2024-07-16 at 12:21 +0300, Baruch Siach wrote:
> Hi Joachim,
> 
> On Tue, Jul 16 2024, Joachim Wiberg wrote:
> > On 2024-07-10 at 23:13 +0200, Thomas Petazzoni wrote:
> > > Applied to master, after adding a reference to the autobuilder
> > > build failure. Thanks!
> > We have the same issue also on 2024.02.x, as of 2024.02.4 builds
> > with libssh break unless you update your defconfig.
> Commit fed58dac5dea (Revert "package/libopenssl: no-engine") should
> have fixed that in 2024.02.4. Are you sure libssh build is still
> broken?

Just retested, and you are 100% correct, the libssh build on 2024.02.x
is *not broken*.

So sorry having wasted everyone's time!

All the best
 /Joachim

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-16 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 20:24 [Buildroot] [PATCH] package/libssh: select BR2_PACKAGE_LIBOPENSSL_ENGINES Heiko Thiery
2024-07-10 14:51 ` Thomas Petazzoni via buildroot
2024-07-10 15:18   ` Heiko Thiery
2024-07-11  0:43   ` Joachim Wiberg
2024-07-10 21:13 ` Thomas Petazzoni via buildroot
2024-07-16  9:10   ` Joachim Wiberg
2024-07-16  9:21     ` Baruch Siach via buildroot
2024-07-16 10:40       ` Joachim Wiberg [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=02e5180ddafe94a9a3d48fdb1dcc8cc2221abeb8.camel@gmail.com \
    --to=troglobit@gmail.com \
    --cc=baruch@tkos.co.il \
    --cc=buildroot@buildroot.org \
    --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.