From: Trevor Woerner <twoerner@gmail.com>
To: linux-kernel@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Gang Yan" <yangang@kylinos.cn>,
"David Disseldorp" <ddiss@suse.de>,
"Miguel Ojeda" <ojeda@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Luis Augenstein" <luis.augenstein@tngtech.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Andrew Jones" <andrew.jones@linux.dev>
Subject: [PATCH] kbuild: let the environment set HOSTPKG_CONFIG
Date: Wed, 5 Aug 2026 01:54:35 -0400 [thread overview]
Message-ID: <20260805055438.3482019-1-twoerner@gmail.com> (raw)
HOSTPKG_CONFIG was added so that "tooling that builds the kernel" could
choose which pkg-config the host tools ask about their dependencies, but
it is assigned with '=', so only a make command line assignment takes
effect. Exporting it does nothing, silently.
That is surprising, because the other inputs to host program builds do
honour the environment: HOSTCFLAGS, HOSTCXXFLAGS, HOSTLDFLAGS and
HOSTLDLIBS are all read from it and documented in kbuild.rst as such.
It also matters. A cross development environment sets
PKG_CONFIG_SYSROOT_DIR and PKG_CONFIG_PATH so that pkg-config answers
for the target rather than the build machine. Those settings are correct
for everything that will run on the target and wrong for a program that
has to run on the build machine. objtool asks pkg-config where libelf is,
gets the target's include directory, and compiles a host tool against
the target's C library headers. Because the directory arrives as -I it
is not treated as a system header directory, -Wno-system-headers no
longer covers it, and the build stops on warnings that would otherwise
be suppressed:
usr/include/sys/cdefs.h:486: error: "__attribute_const__" redefined [-Werror]
tools/include/linux/compiler.h:123: note: previous definition
usr/include/stdio.h:449: error: redundant redeclaration of 'fscanf'
An environment that knows it is cross building can then say
export HOSTPKG_CONFIG="env -u PKG_CONFIG_SYSROOT_DIR \
-u PKG_CONFIG_PATH pkg-config"
once, in the shell it hands to the user, instead of every make command
line growing an override. Build systems that already pass it on the
command line are unaffected.
Assisted-by: Codex:claude-opus-5
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
Documentation/kbuild/kbuild.rst | 5 +++++
Makefile | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/kbuild/kbuild.rst b/Documentation/kbuild/kbuild.rst
index 5a9013bacfb7..6d7de86764be 100644
--- a/Documentation/kbuild/kbuild.rst
+++ b/Documentation/kbuild/kbuild.rst
@@ -110,6 +110,11 @@ HOSTLDLIBS
----------
Additional libraries to link against when building host programs.
+HOSTPKG_CONFIG
+--------------
+The pkg-config to use when building host programs. Set this when cross
+building, where the default would otherwise answer for the target.
+
.. _userkbuildflags:
USERCFLAGS
diff --git a/Makefile b/Makefile
index 902f3f3d54b7..ba64518d5309 100644
--- a/Makefile
+++ b/Makefile
@@ -461,7 +461,7 @@ HOSTCC = gcc
HOSTCXX = g++
endif
HOSTRUSTC = rustc
-HOSTPKG_CONFIG = pkg-config
+HOSTPKG_CONFIG ?= pkg-config
# the KERNELDOC macro needs to be exported, as scripts/Makefile.build
# has a logic to call it
--
2.51.0
next reply other threads:[~2026-08-05 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 5:54 Trevor Woerner [this message]
2026-08-08 5:31 ` [PATCH] kbuild: let the environment set HOSTPKG_CONFIG Nicolas Schier
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=20260805055438.3482019-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=andrew.jones@linux.dev \
--cc=corbet@lwn.net \
--cc=ddiss@suse.de \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=luis.augenstein@tngtech.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yangang@kylinos.cn \
/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