From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] kbuild: deb-pkg: add debarch for ARCH=um
Date: Thu, 12 Dec 2024 10:26:21 +0100 [thread overview]
Message-ID: <20241212-pretty-steadfast-gerbil-cb1edf@lindesnes> (raw)
In-Reply-To: <20241203111459.3331534-1-masahiroy@kernel.org>
On Tue, Dec 03, 2024 at 08:14:45PM +0900, Masahiro Yamada wrote:
> 'make ARCH=um bindeb-pkg' shows the following warning.
>
> $ make ARCH=um bindeb-pkg
> [snip]
> GEN debian
>
> ** ** ** WARNING ** ** **
>
> Your architecture doesn't have its equivalent
> Debian userspace architecture defined!
> Falling back to the current host architecture (amd64).
> Please add support for um to ./scripts/package/mkdebian ...
>
> This commit hard-codes i386/amd64 because UML is only supported for x86.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> scripts/package/mkdebian | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index 4ffcc70f8e31..b038a1380b8a 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -70,6 +70,13 @@ set_debarch() {
> debarch=sh4$(if_enabled_echo CONFIG_CPU_BIG_ENDIAN eb)
> fi
> ;;
> + um)
> + if is_enabled CONFIG_64BIT; then
> + debarch=amd64
> + else
> + debarch=i386
> + fi
> + ;;
> esac
> if [ -z "$debarch" ]; then
> debarch=$(dpkg-architecture -qDEB_HOST_ARCH)
> --
> 2.43.0
>
>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
prev parent reply other threads:[~2024-12-12 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:14 [PATCH] kbuild: deb-pkg: add debarch for ARCH=um Masahiro Yamada
2024-12-12 9:26 ` Nicolas Schier [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=20241212-pretty-steadfast-gerbil-cb1edf@lindesnes \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@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