diff options
author | Miguel Ojeda <ojeda@kernel.org> | 2023-06-16 02:16:30 +0200 |
---|---|---|
committer | Miguel Ojeda <ojeda@kernel.org> | 2023-08-10 01:18:34 +0200 |
commit | bc60c930a43c7c984c80e99282f0d4f7193f3986 (patch) | |
tree | aeca49d58d8c4699b9541227869c514fb0d3aa0a /scripts/rust_is_available_test.py | |
parent | kbuild: rust_is_available: handle failures calling `$RUSTC`/`$BINDGEN` (diff) | |
download | linux-bc60c930a43c7c984c80e99282f0d4f7193f3986.tar.xz linux-bc60c930a43c7c984c80e99282f0d4f7193f3986.zip |
kbuild: rust_is_available: check that output looks as expected
The script already checks for `$RUSTC` and `$BINDGEN` existing
and exiting without failure. However, one may still pass an
unexpected binary that does not output what the later parsing
expects. The script still successfully reports a failure as
expected, but the error is confusing. For instance:
$ RUSTC=true BINDGEN=bindgen CC=clang scripts/rust_is_available.sh
scripts/rust_is_available.sh: 19: arithmetic expression: expecting primary: "100000 * + 100 * + "
***
*** Please see Documentation/rust/quick-start.rst for details
*** on how to set up the Rust support.
***
Thus add an explicit check and a proper message for unexpected
output from the called command.
Similarly, do so for the `libclang` version parsing, too.
Link: https://lore.kernel.org/rust-for-linux/CAK7LNAQYk6s11MASRHW6oxtkqF00EJVqhHOP=5rynWt-QDUsXw@mail.gmail.com/
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
Link: https://lore.kernel.org/r/20230616001631.463536-11-ojeda@kernel.org
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Diffstat (limited to 'scripts/rust_is_available_test.py')
0 files changed, 0 insertions, 0 deletions