You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bash-3.2$ java -Xinternalversion
OpenJDK 64-Bit Server VM (11.0.6+9-jvmci-20.0-b02) for bsd-amd64 JRE (11.0.6+9-jvmci-20.0-b02), built on Jan 20 2020 14:32:51 by "graal1" with gcc 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.2)
bash-3.2$ gcc --version
clang version 9.0.0 (GraalVM.org llvmorg-9.0.0-5-g80b1d876fd-bgb66b241662 80b1d876fd4296b48433de5b66eaebe551897508)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Users/mike/JVMs/graalvm-ce-java11-20.1.0-dev/Contents/Home/lib/llvm/bin
I tried building bash 5.0 with the LLVM toolchain. It fails with this error in the final link step:
Set PATH to be prefixed with the LLVM toolchain directory (languages/llvm/native/bin) and the GraalVM java bin directory.
Run ./configure && make
Investigation
Both these .a files do indeed contain the same .o files exporting the same symbols. This is true of a successful normal build so it seems to be either intentional or harmless usually, but the LLVM toolchain doesn't seem to tolerate it.
The text was updated successfully, but these errors were encountered:
Thanks for giving the toolchain a try! I was able to reproduce the issues with the latest version so did a little digging. Turns out that the issue can be reproduced without using the GraalVM LLVM toolchain. If I compile bash using llvm-ar and llvm-ranlib (which is what our toolchain uses under the hood), I run into the same issue:
closing as it is/was not a graalvm problem. the upstream ticket is not yet closed, but it might be worth trying a newer llvm version. maybe the issue was fixed in the mean time
Using GraalVM EE 20.1-dev on macOS High Sierra
I tried building bash 5.0 with the LLVM toolchain. It fails with this error in the final link step:
It builds fine using a regular macOS toolchain.
Steps to reproduce the problem
./configure && make
Investigation
Both these .a files do indeed contain the same .o files exporting the same symbols. This is true of a successful normal build so it seems to be either intentional or harmless usually, but the LLVM toolchain doesn't seem to tolerate it.
The text was updated successfully, but these errors were encountered: