From: Zhangjin Wu <falcon@tinylab.org>
To: falcon@tinylab.org, w@1wt.eu
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
tanyuan@tinylab.org, thomas@t-8ch.de
Subject: [PATCH v2 0/7] selftests/nolibc: customize CROSS_COMPILE for all supported architectures
Date: Sat, 12 Aug 2023 04:27:01 +0800 [thread overview]
Message-ID: <cover.1691783604.git.falcon@tinylab.org> (raw)
Hi, Willy
Here is v2 of the customized CROSS_COMPILE support, this helps a lot
during the testing of the other cross-arch nolibc changes:
$ ARCHS="i386 x86_64 arm64 arm mips ppc ppc64 ppc64le riscv s390"
$ for arch in ${ARCHS[@]}; do printf "%9s: " $arch; make run-user XARCH=$arch | grep status; done
Based on your suggestion, we did this changes:
- The qemu notes patch [1] is removed, welcome your doc file ;-)
- Arnd's crosstools are customized by default
- Import cc-cross-prefix to support local cross toolchains too
- Use mips64 toolchains for mips like x86_64 toolchains for i386, allow
download less toolchains
- Use HOSTCC for libc-test compiling
Changes from v1 --> v2:
* selftests/nolibc: allow use x86_64 toolchain for i386
No change.
* selftests/nolibc: allow use mips64 toolchain for mips
Allow download less toolchains, save time save storage space
* selftests/nolibc: libc-test: use HOSTCC instead of CC
libc-test is mainly for local test, use HOSTCC
* selftests/nolibc: allow customize CROSS_COMPILE by architecture
Moved the ../../../scripts/Makefile.include after our customized
CROSS_COMPILE, to let it prefix CC with $(CROSS_COMPILE) for us.
* selftests/nolibc: customize CROSS_COMPILE for all architectures
Use Arnd's crosstools as the default ones
* selftests/nolibc: import cc-cross-prefix macro
selftests/nolibc: allow use cross toolchains from software repository
Import cc-cross-prefix to allow customize a list of the cross
compilers, the ones from local repositories are appended in.
If already installed ones from local repos, why not use them, let's
do it.
Willy, since this series is really important to test the coming
patchsets, I send it here before the others to simplify the testing, but
we can delay its review, it is not urgent.
And here [2] is the simple script I wrote to download, decompress and
configure the PATH variable for Anrd's crosstools, hope it helps.
Best regards,
Zhangjin Wu
---
[1]: https://lore.kernel.org/lkml/6de680acbc2d87e13a680d4453ef022568bf489b.1691263493.git.falcon@tinylab.org/
[2]: https://gitee.com/tinylab/linux-lab/blob/next/tools/nolibc/crosstool.sh
v1: https://lore.kernel.org/lkml/cover.1691263493.git.falcon@tinylab.org/
Zhangjin Wu (7):
selftests/nolibc: allow use x86_64 toolchain for i386
selftests/nolibc: allow use mips64 toolchain for mips
selftests/nolibc: libc-test: use HOSTCC instead of CC
selftests/nolibc: allow customize CROSS_COMPILE by architecture
selftests/nolibc: customize CROSS_COMPILE for all architectures
selftests/nolibc: import cc-cross-prefix macro
selftests/nolibc: allow use cross toolchains from software repository
tools/testing/selftests/nolibc/Makefile | 38 +++++++++++++++++++++----
1 file changed, 33 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-11 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 20:27 Zhangjin Wu [this message]
2023-08-11 20:28 ` [PATCH v2 1/7] selftests/nolibc: allow use x86_64 toolchain for i386 Zhangjin Wu
2023-08-11 20:29 ` [PATCH v2 2/7] selftests/nolibc: allow use mips64 toolchain for mips Zhangjin Wu
2023-08-11 20:30 ` [PATCH v2 3/7] selftests/nolibc: libc-test: use HOSTCC instead of CC Zhangjin Wu
2023-08-13 9:19 ` Willy Tarreau
2023-08-11 20:31 ` [PATCH v2 4/7] selftests/nolibc: allow customize CROSS_COMPILE by architecture Zhangjin Wu
2023-08-11 20:32 ` [PATCH v2 5/7] selftests/nolibc: customize CROSS_COMPILE for all architectures Zhangjin Wu
2023-08-13 9:16 ` Willy Tarreau
2023-08-13 10:18 ` Zhangjin Wu
2023-08-14 7:16 ` Willy Tarreau
2023-08-11 20:33 ` [PATCH v2 6/7] selftests/nolibc: import cc-cross-prefix macro Zhangjin Wu
2023-08-11 20:34 ` [PATCH v2 7/7] selftests/nolibc: allow use cross toolchains from software repository Zhangjin Wu
2023-08-13 9:37 ` [PATCH v2 0/7] selftests/nolibc: customize CROSS_COMPILE for all supported architectures Willy Tarreau
2023-08-13 10:05 ` Zhangjin Wu
2023-08-14 7:18 ` Willy Tarreau
2023-08-14 7:38 ` Zhangjin Wu
2023-08-14 8:25 ` Willy Tarreau
2023-08-14 8:25 ` Willy Tarreau
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=cover.1691783604.git.falcon@tinylab.org \
--to=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tanyuan@tinylab.org \
--cc=thomas@t-8ch.de \
--cc=w@1wt.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