From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libmodsecurity: needs host-pkgconf
Date: Fri, 12 Jun 2026 13:37:52 +0200 [thread overview]
Message-ID: <20260612113752.252179-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260531202439.1471287-1-romain.naour@smile.fr>
In reply of:
> The configure script was regenerated for the 3.0.15 release but it now
> error out if pkg-config is missing.
>
> Add host-pkgconf in build dependency.
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/14607335870 (TestNginxModsecurity)
>
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Applied to 2025.02.x & 2026.02.x. Thanks
> ---
> package/libmodsecurity/libmodsecurity.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libmodsecurity/libmodsecurity.mk b/package/libmodsecurity/libmodsecurity.mk
> index c06d890979..8920cb012e 100644
> --- a/package/libmodsecurity/libmodsecurity.mk
> +++ b/package/libmodsecurity/libmodsecurity.mk
> @@ -13,7 +13,7 @@ LIBMODSECURITY_LICENSE_FILES = LICENSE
> LIBMODSECURITY_CPE_ID_VENDOR = trustwave
> LIBMODSECURITY_CPE_ID_PRODUCT = modsecurity
>
> -LIBMODSECURITY_DEPENDENCIES = pcre2
> +LIBMODSECURITY_DEPENDENCIES = pcre2 host-pkgconf
> LIBMODSECURITY_CONF_OPTS = \
> --without-pcre \
> --with-pcre2="$(STAGING_DIR)/usr" \
> --
> 2.54.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-12 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 20:24 [Buildroot] [PATCH] package/libmodsecurity: needs host-pkgconf Romain Naour via buildroot
2026-06-01 9:32 ` Peter Korsgaard
2026-06-12 11:37 ` Thomas Perale 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=20260612113752.252179-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=thomas.perale@mind.be \
/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