The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	linux-kernel@vger.kernel.org,
	"Masahiro Yamada" <masahiroy@kernel.org>
Subject: Re: [RFC PATCH 3/3] tools/nolibc: add a new "install_all_archs" target
Date: Fri, 27 Jun 2025 09:29:44 +0200	[thread overview]
Message-ID: <20250627072944.GD4540@1wt.eu> (raw)
In-Reply-To: <cdf2ebbf-8bfe-40f8-a071-10d56221c202@t-8ch.de>

On Fri, Jun 27, 2025 at 09:27:10AM +0200, Thomas Weißschuh wrote:
> On 2025-06-27 07:49:18+0200, Willy Tarreau wrote:
> > On Fri, Jun 27, 2025 at 07:46:18AM +0200, Willy Tarreau wrote:
> > > On Fri, Jun 27, 2025 at 07:11:45AM +0200, Thomas Weißschuh wrote:
> > > > On 2025-06-26 23:15:07+0200, Arnd Bergmann wrote:
> > > (...)
> > > > With the symlink, a given generic UAPI tree can be specialized to one
> > > > specific architecture. But here we want to create a full sysroot that works
> > > > for all architectures *at the same time*. So a symlink would not be enough.
> > > 
> > > Exactly!
> > > 
> > > > > If it's indeed possible to concatenate the path name (I couldn't
> > > > > figure that out either), that could also be done in place of the
> > > > > symlink but simpler than the #if/#elif/#elif/... block, like
> > > > > 
> > > > > #include <arch.h> // defines ARCH_PREFIX
> > > > > #include CONCAT(ARCH_PREFIX, ioctl.h)
> > > > 
> > > > If we can't get it to work like this I would still prefer to have a
> > > > template header file which gets specialized with sed instead of the
> > > > Makefile loop.
> > > 
> > > The thing is that it's not a single header, it's for each header file
> > > present in asm/. And we can't request that anyone adding anything into
> > > asm would also have to maintain one extra template for each of them.
> > > 
> > > Or I'm simply not getting how you would envision it maybe.
> > 
> > Or do you mean a template that contains all #ifdef/#include for all
> > archs, that serves as the basis to rebuild all headers, and that we
> > still have the loop on all files in the makefile ? I.e. you simply
> > want to drop the arch loop ? If that's it, yes I'm fine with this as
> > well and can give it a try.
> 
> This is exactly what I meant.

OK then, I'll have a look to this and Arnd's idea, hopefully we'll
find something better than the current proposal.

willy

      reply	other threads:[~2025-06-27  7:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 10:37 [RFC PATCH 0/3] tools/nolibc: install unified multi-arch headers Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 1/3] tools/nolibc: merge i386 and x86_64 into a single x86 arch Willy Tarreau
2025-06-21  8:29   ` Thomas Weißschuh
2025-06-21  8:44     ` Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 2/3] tools/nolibc: add a new target "headers_all_archs" to loop over all archs Willy Tarreau
2025-06-23 21:56   ` Thomas Weißschuh
2025-06-24  6:20     ` Willy Tarreau
2025-06-24  7:46       ` Thomas Weißschuh
2025-06-24 10:00         ` Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 3/3] tools/nolibc: add a new "install_all_archs" target Willy Tarreau
2025-06-26 20:18   ` Thomas Weißschuh
2025-06-26 21:15     ` Arnd Bergmann
2025-06-27  3:25       ` Willy Tarreau
2025-06-27  5:58         ` Arnd Bergmann
2025-06-27  6:07           ` Willy Tarreau
2025-06-27  5:11       ` Thomas Weißschuh
2025-06-27  5:46         ` Willy Tarreau
2025-06-27  5:49           ` Willy Tarreau
2025-06-27  7:27             ` Thomas Weißschuh
2025-06-27  7:29               ` Willy Tarreau [this message]

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=20250627072944.GD4540@1wt.eu \
    --to=w@1wt.eu \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=masahiroy@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