[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20261110014154.77227-1-alex@alexrp.com>
Date: Tue, 10 Nov 2026 02:41:54 +0100
From: Alex Rønne Petersen <alex@...xrp.com>
To: musl@...ts.openwall.com
Cc: Alex Rønne Petersen <alex@...xrp.com>
Subject: [PATCH] configure: recognize thumb* target triples as arm
Triples like thumb-linux-musleabi are understood by both clang and
zig cc, and will appear in -dumpmachine. config.sub also recognizes such
triples; it normalizes thumb-* to arm-*, but thumbv7-* is unaltered.
zig cc interprets thumb* triples as really meaning T32-only, which is to
say that -mthumb is implied, unlike clang. So while one could just point
users to arm* triples and -mthumb when running musl's configure with
clang, thumb* triples actually have meaningfully different semantics
with zig cc, making it useful for musl's configure to recognize them.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index bc9fbe48..d1a1ae32 100755
--- a/configure
+++ b/configure
@@ -321,7 +321,7 @@ printf "%s\n" "$target"
#
case "$target" in
# Catch these early to simplify matching for 32-bit archs
-arm*) ARCH=arm ;;
+arm*|thumb*) ARCH=arm ;;
aarch64*) ARCH=aarch64 ;;
i?86-nt32*) ARCH=nt32 ;;
i?86*) ARCH=i386 ;;
--
2.53.0
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
