From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Nicolas Schier <nsc@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [PATCH v3 0/3] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags
Date: Fri, 14 Nov 2025 14:43:55 +0100 [thread overview]
Message-ID: <20251114-kbuild-userprogs-bits-v3-0-4dee0d74d439@linutronix.de> (raw)
The current logic to inherit -m32/-m64 from the kernel build only works
for a few architectures. It does not handle byte order differences,
architectures using different compiler flags or different kinds of ABIs.
Introduce a per-architecture override mechanism to set CC_CAN_LINK and
the flags used for userprogs.
This revision only contains the generic kbuild infrastructure bits.
The architecture-specific will go through the architecture trees.
They are present in v2 of the series linked below.
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
Changes in v3:
- Drop all architecture-specific patches, they will go in through the architecture trees.
- Trim recipient list.
- Fix old reference to CONFIG_ARCH_USERPROGS_CFLAGS
- Link to v2: https://lore.kernel.org/r/20251014-kbuild-userprogs-bits-v2-0-faeec46e887a@linutronix.de
Changes in v2:
- Rebase and drop already applied patch
- Disable CC_CAN_LINK if the test program generates warnings
- Move to architecture-specific logic
- Link to v1: https://lore.kernel.org/r/20250813-kbuild-userprogs-bits-v1-0-2d9f7f411083@linutronix.de
---
Thomas Weißschuh (3):
kbuild: don't enable CC_CAN_LINK if the dummy program generates warnings
init: deduplicate cc-can-link.sh invocations
kbuild: allow architectures to override CC_CAN_LINK
Makefile | 13 +++++++++++--
init/Kconfig | 8 ++++++--
scripts/Kconfig.include | 3 +++
scripts/cc-can-link.sh | 2 +-
4 files changed, 21 insertions(+), 5 deletions(-)
---
base-commit: 10f8210c7a7098897fcee5ca70236167b39eb797
change-id: 20250813-kbuild-userprogs-bits-03c117da4d50
Best regards,
--
Thomas Weißschuh <thomas.weissschuh@linutronix.de>
next reply other threads:[~2025-11-14 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 13:43 Thomas Weißschuh [this message]
2025-11-14 13:43 ` [PATCH v3 1/3] kbuild: don't enable CC_CAN_LINK if the dummy program generates warnings Thomas Weißschuh
2025-11-14 13:43 ` [PATCH v3 2/3] init: deduplicate cc-can-link.sh invocations Thomas Weißschuh
2025-11-14 13:43 ` [PATCH v3 3/3] kbuild: allow architectures to override CC_CAN_LINK Thomas Weißschuh
2025-11-19 11:58 ` [PATCH v3 0/3] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags 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=20251114-kbuild-userprogs-bits-v3-0-4dee0d74d439@linutronix.de \
--to=thomas.weissschuh@linutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=nsc@kernel.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;
as well as URLs for NNTP newsgroup(s).