public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Ben Hutchings <ben@decadent.org.uk>,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH 0/4] kbuild: cross-compile linux-headers package
Date: Sat, 27 Jul 2024 16:42:00 +0900	[thread overview]
Message-ID: <20240727074526.1771247-1-masahiroy@kernel.org> (raw)


This series makes cross-built linux-headers package usable in the
installed system. Currently, host programs in it are built for the
build machine instead of the target architecture.

The first two patches refactors modpost. The endianness in modpost is
currently determined at compile-time, but the build machine cannot
execute scripts/mod/mk_elfconfig compiled for a forein architecture.

The last patch rebuilds scripts/ for the target architecture.



Masahiro Yamada (4):
  modpost: remove unused HOST_ELFCLASS
  modpost: detect endianness on run-time
  kbuild: slim down package for building external modules
  kbuild: cross-compile linux-headers package when possible

 scripts/mod/mk_elfconfig.c           | 25 -------------
 scripts/mod/modpost.c                | 36 +++++++++++++++++++
 scripts/mod/modpost.h                | 13 +++----
 scripts/package/install-extmod-build | 54 +++++++++++++++++++++++++---
 4 files changed, 89 insertions(+), 39 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-07-27  7:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27  7:42 Masahiro Yamada [this message]
2024-07-27  7:42 ` [PATCH 1/4] modpost: remove unused HOST_ELFCLASS Masahiro Yamada
2024-07-31 20:43   ` Nicolas Schier
2024-07-27  7:42 ` [PATCH 2/4] modpost: detect endianness on run-time Masahiro Yamada
2024-07-31 20:47   ` Nicolas Schier
2024-07-27  7:42 ` [PATCH 3/4] kbuild: slim down package for building external modules Masahiro Yamada
2024-07-31 21:01   ` Nicolas Schier
2024-08-24 12:27   ` Thomas Weißschuh
2024-08-24 16:58     ` Masahiro Yamada
2025-02-18 20:25   ` Jeffrey Hugo
2025-02-20 10:03     ` Nicolas Schier
2025-02-20 15:03       ` Jeffrey Hugo
2025-02-20 15:54         ` Nicolas Schier
2025-02-20 16:31           ` Jeffrey Hugo
2025-02-20 16:49             ` Greg KH
2025-02-20 17:24               ` Jeffrey Hugo
2025-02-20 17:43                 ` Greg KH
2025-02-20 18:12                   ` Masahiro Yamada
2025-02-28 22:04                   ` Jeffrey Hugo
2025-02-20 17:57                 ` Masahiro Yamada
2024-07-27  7:42 ` [PATCH 4/4] kbuild: cross-compile linux-headers package when possible Masahiro Yamada
2024-07-30  1:03   ` Kees Cook
2024-08-01  2:26     ` Masahiro Yamada
2024-07-31 21:10   ` Nicolas Schier
2024-08-01  2:37     ` Masahiro Yamada
2024-08-01  7:04       ` Nicolas Schier
2024-10-17 14:45   ` Ron Economos
2024-10-17 19:24     ` Nicolas Schier
2024-10-17 19:34       ` Ron Economos
2024-11-14 20:57         ` Charlie Jenkins
2024-11-16  8:03           ` Masahiro Yamada

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=20240727074526.1771247-1-masahiroy@kernel.org \
    --to=masahiroy@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=kees@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    /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