From: Nicolas Schier <nsc@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"David Gow" <davidgow@google.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kbuild@vger.kernel.org,
automated-testing@lists.yoctoproject.org,
workflows@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds
Date: Tue, 27 Jan 2026 21:13:44 +0100 [thread overview]
Message-ID: <aXkceKDeYxUGHLQh@levanger> (raw)
In-Reply-To: <56209dbc-2dbe-4f52-a703-bcbd9ed3e712@gtucker.io>
On Thu, Jan 22, 2026 at 03:12:36PM +0100, Guillaume Tucker wrote:
> Hi Nicolas,
>
> On 20/01/2026 14:54, Nicolas Schier wrote:
> > Out-of-source builds do not work on my system with podman. If this is
> > expected, I think it would be great to mention that somewhere in the
> > documentation.
>
> The v4 now mentions this and also includes a trick using bind-mount:
>
> mkdir -p $HOME/tmp/my-kernel-build
> mkdir -p build
> sudo mount --bind $HOME/tmp/my-kernel-build build
> scripts/container -i kernel.org/gcc -- make mrproper
> scripts/container -i kernel.org/gcc -- make O=build defconfig
> scripts/container -i kernel.org/gcc -- make O=build -j$(nproc)
>
> Would this work for your use-case? Directory names are entirely
> arbitrary. It's not ideal but might be good enough as a workaround
> until this gets properly supported by the tool in a future version.
sorry for the long delay. Yes, thanks for the follow-up!
Kind regards,
Nicolas
next prev parent reply other threads:[~2026-01-27 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 16:51 [PATCH v3 0/2] scripts: introduce containerized builds Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 1/2] scripts: add tool to run " Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 2/2] Documentation: dev-tools: add container.rst page Guillaume Tucker
2026-01-20 13:53 ` Nicolas Schier
2026-01-20 18:35 ` Nathan Chancellor
2026-01-20 18:39 ` Nathan Chancellor
2026-01-21 9:55 ` Guillaume Tucker
2026-01-22 4:55 ` Nathan Chancellor
2026-01-22 14:25 ` Guillaume Tucker
2026-01-22 10:13 ` Guillaume Tucker
2026-01-16 10:28 ` [PATCH v3 0/2] scripts: introduce containerized builds Guillaume Tucker
2026-01-16 21:12 ` Nathan Chancellor
2026-01-19 14:22 ` Guillaume Tucker
2026-01-19 21:35 ` Nathan Chancellor
2026-01-19 21:49 ` Nathan Chancellor
2026-01-20 9:56 ` Guillaume Tucker
2026-01-20 17:58 ` Nathan Chancellor
2026-01-20 9:46 ` Guillaume Tucker
2026-01-20 17:55 ` Nathan Chancellor
2026-01-20 13:54 ` Nicolas Schier
2026-01-20 18:04 ` Nathan Chancellor
2026-01-21 10:13 ` Guillaume Tucker
2026-01-22 14:12 ` Guillaume Tucker
2026-01-27 20:13 ` Nicolas Schier [this message]
2026-01-31 13:36 ` Guillaume Tucker
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=aXkceKDeYxUGHLQh@levanger \
--to=nsc@kernel.org \
--cc=arnd@arndb.de \
--cc=automated-testing@lists.yoctoproject.org \
--cc=davidgow@google.com \
--cc=gtucker@gtucker.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=work@onurozkan.dev \
--cc=workflows@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.