From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org, tim.hammer@nav-timing.safrangroup.com,
nicolas.carrier@nav-timing.safrangroup.com
Subject: Re: [Buildroot] [PATCH v3 2/5] package/libcurl: Reapply "libcurl: add host variant"
Date: Thu, 12 Feb 2026 23:35:48 +0100 [thread overview]
Message-ID: <aY5VrfmnkY8yD3bw@windsurf> (raw)
In-Reply-To: <20251016-openscap-v3-2-d7b28e958f5f@bootlin.com>
On Thu, Oct 16, 2025 at 04:46:35PM +0200, Alexis Lothoré via buildroot wrote:
> libcurl host build support has initially been added with 736e0fc5d610
> ("libcurl: add host variant") while adding support for host-cargo build,
> and reverted with 69e84008abf8 ("Revert "libcurl: add host variant"")
> when standalone cargo build has been removed. In order to bring a new
> host package depending on libcurl, re-enable host-libcurl build support.
> While doing so, remove the not-needed-anymore post-patch hook.
Applied with some slight rewording of the commit message.
Thanks a lot!
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
next prev parent reply other threads:[~2026-02-12 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 14:46 [Buildroot] [PATCH v3 0/5] package/compliance-as-code: introduce new package Alexis Lothoré via buildroot
2025-10-16 14:46 ` [Buildroot] [PATCH v3 1/5] package/libxmlsec1: " Alexis Lothoré via buildroot
2026-02-10 22:52 ` Thomas Petazzoni via buildroot
2025-10-16 14:46 ` [Buildroot] [PATCH v3 2/5] package/libcurl: Reapply "libcurl: add host variant" Alexis Lothoré via buildroot
2026-02-12 22:35 ` Thomas Petazzoni via buildroot [this message]
2025-10-16 14:46 ` [Buildroot] [PATCH v3 3/5] package/openscap: new package Alexis Lothoré via buildroot
2026-02-12 22:36 ` Thomas Petazzoni via buildroot
2025-10-16 14:46 ` [Buildroot] [PATCH v3 4/5] package/compliance-as-code: " Alexis Lothoré via buildroot
2025-10-16 14:46 ` [Buildroot] [PATCH v3 5/5] support/testing: add runtime testing for compliance-as-code Alexis Lothoré via buildroot
2025-10-29 16:44 ` [Buildroot] [PATCH v3 0/5] package/compliance-as-code: introduce new package Tim Hammer
2025-11-17 14:25 ` Alexis Lothoré via buildroot
2026-01-23 9:04 ` Alexis Lothoré via buildroot
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=aY5VrfmnkY8yD3bw@windsurf \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=nicolas.carrier@nav-timing.safrangroup.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tim.hammer@nav-timing.safrangroup.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