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 5/8] lfs/Config: Set GOARCH for loongarch64 builds
Date: Tue, 4 Aug 2026 19:39:53 -0700 [thread overview]
Message-ID: <20260805023956.3379890-6-vincent.mc.li@gmail.com> (raw)
In-Reply-To: <20260805023956.3379890-1-vincent.mc.li@gmail.com>
Define GOARCH=loong64 for loongarch64 architecture builds to enable
proper Go language compilation support. The Go programming language
uses "loong64" as the architecture identifier for LoongArch 64-bit
systems.
This allows any Go packages in the build system to compile correctly
for the loongarch64 target by providing the correct GOARCH value during
the build process.
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
---
lfs/Config | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/lfs/Config b/lfs/Config
index 06ba065ea..fea0fcbbd 100644
--- a/lfs/Config
+++ b/lfs/Config
@@ -157,6 +157,10 @@ ifeq "$(BUILD_ARCH)" "aarch64"
GOARCH = arm64
endif
+ifeq "$(BUILD_ARCH)" "loongarch64"
+ GOARCH = loong64
+endif
+
# Rust
ifeq "$(BUILD_ARCH)" "riscv64"
RUST_ARCH = riscv64gc
--
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 ` [PATCH v1 1/8] make.sh: Add support for building on loongarch64 Vincent Li
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 ` Vincent Li [this message]
2026-08-05 2:39 ` [PATCH v1 6/8] installer: Enable EFI support " 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-6-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