-
Bug
-
Resolution: Fixed
-
P3
-
24
-
None
-
master
After JDK-8338304, we are seeing tool from Clang GCC installation is being picked up unexpectedly (JDK build configured with `--with-toolchain-type=clang`). In the specific case, user supplied compiler toolchain is used by setting `CXX=<user_specified_path_to_tools_script>` during configuration, for example. Apparently, `UTIL_REQUIRE_PROGS(LLD, lld)` is not able to resolve `lld` properly in this case.
```
Found candidate GCC installation: <snip>
Selected GCC installation: <snip>
...
clang: error: unsupported option '-V -static-libgcc'
configure:85215: $? = 1
configure:85204: <snip> -qversion >&5
clang: error: unknown argument '-qversion'; did you mean '--version'?
...
```
I've tested with a change to not do `UTIL_REQUIRE_PROGS(LLD, lld)` in the case where user specified toolchain should be used with more complex compilation environment. That reverts back to the previous behavior and works without issue for user specified toolchain usages.
```
Found candidate GCC installation: <snip>
Selected GCC installation: <snip>
...
clang: error: unsupported option '-V -static-libgcc'
configure:85215: $? = 1
configure:85204: <snip> -qversion >&5
clang: error: unknown argument '-qversion'; did you mean '--version'?
...
```
I've tested with a change to not do `UTIL_REQUIRE_PROGS(LLD, lld)` in the case where user specified toolchain should be used with more complex compilation environment. That reverts back to the previous behavior and works without issue for user specified toolchain usages.
- relates to
-
JDK-8333189 Make sure clang on linux uses lld as linker
- Resolved
-
JDK-8338304 clang on Linux - check for lld presence after JDK-8333189
- Resolved
- links to
-
Commit(master) openjdk/jdk/8c1cf8fa
-
Review(master) openjdk/jdk/21817