From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] Makefile: Fix for 'make CFLAGS=...'
Date: Tue, 9 Sep 2025 11:57:14 +0200 [thread overview]
Message-ID: <aL_5-hgKWiF877pb@calendula> (raw)
In-Reply-To: <20250908221909.31384-1-phil@nwl.cc>
On Tue, Sep 09, 2025 at 12:19:09AM +0200, Phil Sutter wrote:
> Appending to CFLAGS from configure.ac like this was too naive, passing
> custom CFLAGS in make arguments overwrites it. Extend AM_CFLAGS instead.
>
> Fixes: 64c07e38f0494 ("table: Embed creating nft version into userdata")
> Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
Thanks for fixing this.
> ---
> Makefile.am | 2 ++
> configure.ac | 1 -
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Makefile.am b/Makefile.am
> index 5190a49ae69f1..3e3f1e61092bb 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -156,6 +156,8 @@ AM_CFLAGS = \
> \
> $(GCC_FVISIBILITY_HIDDEN) \
> \
> + -DMAKE_STAMP=$(MAKE_STAMP) \
> + \
> $(NULL)
>
> AM_YFLAGS = -d -Wno-yacc
> diff --git a/configure.ac b/configure.ac
> index da16a6e257c91..3517ea041f7ea 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -153,7 +153,6 @@ AC_CONFIG_COMMANDS([nftversion.h], [
> # Current date should be fetched exactly once per build,
> # so have 'make' call date and pass the value to every 'gcc' call
> AC_SUBST([MAKE_STAMP], ["\$(shell date +%s)"])
> -CFLAGS="${CFLAGS} -DMAKE_STAMP=\${MAKE_STAMP}"
>
> AC_CONFIG_FILES([ \
> Makefile \
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-09-09 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 22:19 [nft PATCH] Makefile: Fix for 'make CFLAGS=...' Phil Sutter
2025-09-09 9:57 ` Pablo Neira Ayuso [this message]
2025-09-09 10:19 ` 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=aL_5-hgKWiF877pb@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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