From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>, Zhangjin Wu <falcon@tinylab.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/6] tools/nolibc: error out on unsupported architecture
Date: Sun, 5 Nov 2023 11:36:54 +0100 [thread overview]
Message-ID: <ZUdwRuOuKQxzoh8a@1wt.eu> (raw)
In-Reply-To: <20231105-nolibc-mips-be-v1-1-6c2ad3e50a1f@weissschuh.net>
On Sun, Nov 05, 2023 at 11:09:55AM +0100, Thomas Weißschuh wrote:
> When an architecture is unsupported arch.h would silently continue.
> This leads to a lot of followup errors because my_syscallX() is not
> defined and the startup code is missing.
>
> Avoid these confusing errors and fail the build early with a clear
> error message and location.
Oops, good catch!
Thanks,
Willy
next prev parent reply other threads:[~2023-11-05 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 10:09 [PATCH 0/6] tools/nolibc: MIPS bugfixes and refactoring Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 1/6] tools/nolibc: error out on unsupported architecture Thomas Weißschuh
2023-11-05 10:36 ` Willy Tarreau [this message]
2023-11-05 10:09 ` [PATCH 2/6] tools/nolibc: move MIPS ABI validation into arch-mips.h Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 3/6] selftests/nolibc: use XARCH for MIPS Thomas Weißschuh
2023-11-05 10:32 ` Willy Tarreau
2023-11-05 10:49 ` Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 4/6] selftests/nolibc: explicitly specify ABI " Thomas Weißschuh
2023-11-05 10:09 ` [PATCH 5/6] selftests/nolibc: extraconfig support Thomas Weißschuh
2023-11-05 10:35 ` Willy Tarreau
2023-11-05 10:10 ` [PATCH 6/6] selftests/nolibc: add configuration for mipso32be Thomas Weißschuh
2023-11-05 10:37 ` [PATCH 0/6] tools/nolibc: MIPS bugfixes and refactoring 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=ZUdwRuOuKQxzoh8a@1wt.eu \
--to=w@1wt.eu \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@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