From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/socat: support OpenSSL only
Date: Fri, 11 Nov 2022 23:50:31 +0100 [thread overview]
Message-ID: <20221111235031.04029345@windsurf> (raw)
In-Reply-To: <3e8e93e9eed117bc7e49580fd77e254eee237a99.1668060990.git.baruch@tkos.co.il>
On Thu, 10 Nov 2022 08:16:30 +0200
Baruch Siach via buildroot <buildroot@buildroot.org> wrote:
> socat is not compatible with libressl.
>
> Fixes:
> http://autobuild.buildroot.net/results/6f0204004c52f762d6e3cb3064238d7eb3646038/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/socat/socat.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've applied to next, but after cherry-picking from master the change
in socat disabling the use of OpenSSL with static configurations. This
way, I resolved the conflict right away, while the topic is fresh. I
also expanded your commit log, which forgot to indicate since when the
problem occurs (it was in your follow-up e-mail).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-11 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 6:16 [Buildroot] [PATCH] package/socat: support OpenSSL only Baruch Siach via buildroot
2022-11-10 10:15 ` Baruch Siach via buildroot
2022-11-11 22:50 ` 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=20221111235031.04029345@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.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.