From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libcurl: fix build with wolfssl
Date: Sat, 30 May 2026 17:15:01 +0200 [thread overview]
Message-ID: <ahr8IZ-dp4xDNGjC@windsurf> (raw)
In-Reply-To: <ec612e55099118043d351762107b9c1a18387130.1775471071.git.baruch@tkos.co.il>
On Mon, Apr 06, 2026 at 01:24:31PM +0300, Baruch Siach via buildroot wrote:
> wolfssl requires definition of SIZEOF_LONG_LONG. Commit 3a5e071e4f9
> ("package/libcurl: security bump to version 8.19.0") removed
> SIZEOF_LONG_LONG definitions from libcurl autotools build system,
> breaking build with wolfssl.
>
> Add a patch to restore SIZEOF_LONG_LONG.
>
> Fixes:
> https://autobuild.buildroot.org/results/54140f8139f40a708afd25cd0264b52c7a9bf332
> https://autobuild.buildroot.org/results/07fa4932fe247e8e472f0f134db6ec36421303e4
> https://autobuild.buildroot.org/results/c0c64b348b5fbaa77ecc117078cbad8ecb9c4941
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
My understanding is that upstream rejected this fix, and instead
suggested to fix WolfSSL, which was done in Buildroot in commit:
50feb8738464448c74a7e51e037716fa6a2f38f3 package/wolfssl: fix build with libcurl >= 8.19.0
So I'll mark this patch as Rejected in patchwork.
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-05-30 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 10:24 [Buildroot] [PATCH] package/libcurl: fix build with wolfssl Baruch Siach via buildroot
2026-05-30 15:15 ` 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=ahr8IZ-dp4xDNGjC@windsurf \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--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