When a language is enabled but we run the testsuite against a tree in
which the frontend compiler is not present, help.exp fails. It
recognizes the output pattern for a disabled language, but not a
missing frontend. Extend the pattern so that it covers both cases.
Tested on x86_64-linux-gnu. Ok to install?
for gcc/testsuite/ChangeLog
* lib/options.exp (check_for_options_with_filter): Handle
missing frontend compiler like disabled language.
---
gcc/testsuite/lib/options.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/lib/options.exp b/gcc/testsuite/lib/options.exp
index 30e6e50d703dc..a4b15c14f9c6c 100644
--- a/gcc/testsuite/lib/options.exp
+++ b/gcc/testsuite/lib/options.exp
@@ -59,7 +59,7 @@ proc check_for_options_with_filter { language gcc_options
exclude \
set gcc_output [gcc_target_compile $srcfname $filebase.x executable
$gcc_options]
remote_file build delete $srcfname $filebase.x $filebase.gcno
- if {[regexp -- "compiler not installed on this system" $gcc_output]} {
+ if {[regexp -- "compiler not installed on this system|cannot execute"
$gcc_output]} {
unsupported "$test: $language compiler not available"
return
}
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
