From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next v2 1/1] package/uhttpd: bump version, fix cmake 4 compatibility
Date: Thu, 20 Aug 2026 22:41:28 +0200 [thread overview]
Message-ID: <aodmZpj2VIl4gQwe@windsurf> (raw)
In-Reply-To: <20260527185007.3533507-1-bernd@kuhls.net>
On Wed, May 27, 2026 at 08:50:07PM +0200, Bernd Kuhls wrote:
> This bump includes upstream commit
> https://git.openwrt.org/?p=project/uhttpd.git;a=commitdiff;h=ebb92e6b339b88bbc6b76501b6603c52d4887ba1
> which fixes cmake 4 builds. No backports necessary because the cmake 4
> bump commit e46695bbe4ab583f39f9448f3ef3e044efa28808 is not present in
> any older branches.
>
> Updated hash of header file which is used as license file due to
> upstream commits:
> https://github.com/openwrt/uhttpd/commits/master/uhttpd.h
>
> Disabled new configure option UCODE_SUPPORT which was added by upstream
> commit:
> https://git.openwrt.org/?p=project/uhttpd.git;a=commitdiff;h=3ceccd02d86bf4d6609f46d8b30963cc52034cc2
>
> Fixes:
> https://autobuild.buildroot.net/results/cc2/cc265d34aed684b88032edd04ca0fc88186ec676/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master (because it fixes a build issue), 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
prev parent reply other threads:[~2026-08-20 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:50 [Buildroot] [PATCH/next v2 1/1] package/uhttpd: bump version, fix cmake 4 compatibility Bernd Kuhls
2026-08-20 20:41 ` 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=aodmZpj2VIl4gQwe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox