From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Jianhui Zhao <zhaojh329@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libuhttpd: fix build with openssl3
Date: Thu, 20 Jul 2023 23:18:51 +0200 [thread overview]
Message-ID: <20230720231851.5beb0f3f@windsurf> (raw)
In-Reply-To: <20230720202632.2567755-1-bernd@kuhls.net>
On Thu, 20 Jul 2023 22:26:32 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/c09/c09c77e399e9ee410995a91a22306897eca667d1/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> ...eLists.txt-remove-Werror-from-CFLAGS.patch | 38 +++++++++++++++++++
> ...eLists.txt-remove-Werror-from-CFLAGS.patch | 38 +++++++++++++++++++
> 2 files changed, 76 insertions(+)
> create mode 100644 package/libuhttpd/0002-CMakeLists.txt-remove-Werror-from-CFLAGS.patch
> create mode 100644 package/libuhttpd/0003-CMakeLists.txt-remove-Werror-from-CFLAGS.patch
Applied to master, thanks. However, I don't think your two patches are
acceptable upstream: the right change for upstream is to fix the usage
of the deprecated OpenSSL functions.
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:[~2023-07-20 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 20:26 [Buildroot] [PATCH 1/1] package/libuhttpd: fix build with openssl3 Bernd Kuhls
2023-07-20 21:18 ` 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=20230720231851.5beb0f3f@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=zhaojh329@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox