From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>,
"Shuah Khan" <shuah@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 04/12] kbuild: userprogs: add nolibc support
Date: Sat, 22 Feb 2025 10:44:40 +0100 [thread overview]
Message-ID: <20250222094440.GB13258@1wt.eu> (raw)
In-Reply-To: <20250217-kunit-kselftests-v1-4-42b4524c3b0a@linutronix.de>
On Mon, Feb 17, 2025 at 11:59:24AM +0100, Thomas Weißschuh wrote:
> Userprogs are built with the regular kernel compiler $CC.
> A kernel compiler does not necessarily contain a libc which is required
> for a normal userspace application.
> However the kernel tree does contain a minimal libc implementation
> "nolibc" which can be used to build userspace applications.
>
> Introduce support to build userprogs against nolibc instead of the
> default C of the compiler, which may not exist.
^^^
"C library" or maybe "libc" I guess here.
Willy
next prev parent reply other threads:[~2025-02-22 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:59 [PATCH 00/12] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 01/12] kconfig: implement CONFIG_HEADERS_INSTALL for Usermode Linux Thomas Weißschuh
2025-03-02 17:06 ` Masahiro Yamada
2025-03-04 19:23 ` Masahiro Yamada
2025-02-17 10:59 ` [PATCH 02/12] kconfig: introduce CONFIG_ARCH_HAS_NOLIBC Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 03/12] kbuild: userprogs: respect CONFIG_WERROR Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 04/12] kbuild: userprogs: add nolibc support Thomas Weißschuh
2025-02-22 9:44 ` Willy Tarreau [this message]
2025-02-17 10:59 ` [PATCH 05/12] kbuild: introduce blob framework Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 06/12] kunit: tool: Add test for nested test result reporting Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 07/12] kunit: tool: Don't overwrite test status based on subtest counts Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 08/12] kunit: tool: Parse skipped tests from kselftest.h Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 09/12] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 10/12] kunit: uapi: Add example for UAPI tests Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 11/12] kunit: uapi: Introduce preinit executable Thomas Weißschuh
2025-02-17 10:59 ` [PATCH 12/12] kunit: uapi: Validate usability of /proc Thomas Weißschuh
2025-02-18 8:20 ` [PATCH 00/12] kunit: Introduce UAPI testing framework David Gow
2025-02-18 8:57 ` Thomas Weißschuh
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=20250222094440.GB13258@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=rmoar@google.com \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®