From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] Makefile: Set PKG_CONFIG_PATH env for 'make check'
Date: Thu, 5 Feb 2026 15:24:14 +0100 [thread overview]
Message-ID: <aYSoDgjTbH9t5Na6@orbyte.nwl.cc> (raw)
In-Reply-To: <aYPzQOgGxpacVYMV@chamomile>
On Thu, Feb 05, 2026 at 02:32:48AM +0100, Pablo Neira Ayuso wrote:
> On Tue, Jan 27, 2026 at 11:15:58PM +0100, Phil Sutter wrote:
> > When building nftables git HEAD, I use a script which also builds libmnl
> > and libnftnl in their respective repositories and populates
> > PKG_CONFIG_PATH variable so nftables is linked against them instead of
> > host libraries. This is mandatory as host-installed libraries are
> > chronically outdated and linking against them would fail.
>
> How do you use this?
Please kindly find aforementioned build script attached to this mail.
Then I just call 'make check' in the built nftables source tree.
This patch's logic is: "If a custom PKG_CONFIG_PATH was needed to build
the sources, it is needed for build test suite as well."
> > Same situation exists with build test suite. Luckily the PKG_CONFIG_PATH
> > variable value used to build the project is cached in Makefiles and
> > Automake supports populating test runners' environment.
> >
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > ---
> > Pablo: Could you please confirm this does not break your workflow? I
> > recall you relied upon build test suite while it never passed for me due
> > to the reasons described above.
>
> Just run `make distcheck' or tests/build/ to check, I think that
> should be enough.
Well, 'make distcheck' should not be affected by this patch since it
does not run the test suites (df19bf51d49be ("Makefile: Enable support
for 'make check'")).
But you have a point there, the logic from above applies to the VPATH
build performed by 'make distcheck', too. I'll respin with added chunk:
| --- a/Makefile.am
| +++ b/Makefile.am
| @@ -23,7 +23,8 @@ libnftables_LIBVERSION = 2:0:1
| ###############################################################################
|
| ACLOCAL_AMFLAGS = -I m4
| -AM_DISTCHECK_CONFIGURE_FLAGS = --enable-distcheck
| +AM_DISTCHECK_CONFIGURE_FLAGS = --enable-distcheck \
| + PKG_CONFIG_PATH=$(PKG_CONFIG_PATH)
|
| EXTRA_DIST =
| BUILT_SOURCES =
Thanks, Phil
next prev parent reply other threads:[~2026-02-05 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 22:15 [nft PATCH] Makefile: Set PKG_CONFIG_PATH env for 'make check' Phil Sutter
2026-02-05 1:32 ` Pablo Neira Ayuso
2026-02-05 14:24 ` Phil Sutter [this message]
2026-02-05 14:27 ` Phil Sutter
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=aYSoDgjTbH9t5Na6@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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