-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
solc on linux is dynamically linked #10
Comments
Good point @tbocek. Latest version I guess? |
@mkalinin Yes, latest version. I tried to replace STATIC_LINKING with SOLC_LINK_STATIC in the dockerfile, but its still dynamically linked. |
@tbocek could you make a fix for that? |
Or even better to make a build for |
@mkalinin I started to work on that, and I'm wondering why not just take the libraries from https://github.com/ethereum/solidity/releases. Was there a reason to not use those? |
@tbocek great! 👍 There was no reason for that. I am pretty sure those libs will work. But previous update wasn't done by our team and I just can't say why updater hasn't used libs from solc release. |
@mkalinin alright! I did some changes here: https://github.com/tbocek/solcJ/ |
I believe he can install it using this guide https://solidity.readthedocs.io/en/latest/installing-solidity.html#binary-packages and get installed binaries |
We will try, if we also get a huge binary, we'll go with that one. |
Addressed in #12 |
The resulting binary should work on any Linux platform, and should look as follows:
$ file solc soltest
solc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
soltest: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
However, the current file looks as follows:
$ file solc
solc: ELF 64-bit LSB pie executable x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, stripped
That means it does not run where libmusl is not installed.
When running the build script run.sh, the following output shows the problem:
The text was updated successfully, but these errors were encountered: