From: Vincent Li <vincent.mc.li@gmail.com>
To: Michael Tremer <michael.tremer@ipfire.org>, development@lists.ipfire.org
Cc: Vincent Li <vincent.mc.li@gmail.com>
Subject: [PATCH v1 1/8] make.sh: Add support for building on loongarch64
Date: Tue, 4 Aug 2026 19:39:49 -0700 [thread overview]
Message-ID: <20260805023956.3379890-2-vincent.mc.li@gmail.com> (raw)
In-Reply-To: <20260805023956.3379890-1-vincent.mc.li@gmail.com>
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
---
make.sh | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/make.sh b/make.sh
index 37f01c1a2..fd8b777a3 100755
--- a/make.sh
+++ b/make.sh
@@ -49,6 +49,7 @@ KVER="${KVER/-rc/.0-rc}${KVER_SUFFIX}"
# All supported architectures
ARCHES=(
aarch64
+ loongarch64
riscv64
x86_64
)
@@ -2415,7 +2416,7 @@ done
# Check the architecture
case "${BUILD_ARCH}" in
- aarch64|x86_64|riscv64)
+ aarch64|x86_64|riscv64|loongarch64)
;;
*)
@@ -2429,6 +2430,10 @@ case "${BUILD_ARCH}" in
BUILD_PLATFORM="arm"
;;
+ loongarch64)
+ BUILD_PLATFORM="loongarch"
+ ;;
+
riscv64)
BUILD_PLATFORM="riscv"
;;
--
2.38.1
next prev parent reply other threads:[~2026-08-05 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 2:39 [PATCH v1 0/8] Add loongarch64 architecture support to IPFire Vincent Li
2026-08-05 2:39 ` Vincent Li [this message]
2026-08-05 2:39 ` [PATCH v1 2/8] gcc: Add dynamic linker path for loongarch64 native toolchain build Vincent Li
2026-08-05 2:39 ` [PATCH v1 3/8] lfs/Config: Update config.guess and config.sub for loongarch64 support Vincent Li
2026-08-05 2:39 ` [PATCH v1 4/8] lfs/Config: Add EFI and GRUB architecture definitions for loongarch64 Vincent Li
2026-08-05 2:39 ` [PATCH v1 5/8] lfs/Config: Set GOARCH for loongarch64 builds Vincent Li
2026-08-05 2:39 ` [PATCH v1 6/8] installer: Enable EFI support for loongarch64 Vincent Li
2026-08-05 2:39 ` [PATCH v1 7/8] installer: Add bootloader installation " Vincent Li
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=20260805023956.3379890-2-vincent.mc.li@gmail.com \
--to=vincent.mc.li@gmail.com \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.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