solc-bin issue: one commit for different versions?
See original GitHub issueTwo files in bin folder with same commit but with different content, is it was error or was made intentionally?
md5sum .soljson/*4457170*
40087b0c6c5772221bf09e76d311fe74 .soljson/soljson-v0.1.3-nightly.2015.9.25+commit.4457170.js
cc36e9b9ff0abf281068b5bdfad707db .soljson/soljson-v0.1.3-nightly.2015.9.28+commit.4457170.js
Also, few files have stable and nightly builds: 7dab890
, 4dc1cb1
, 81ae2a7
Why issues is not available in https://github.com/ethereum/solc-bin ?
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Linux binary for version 0.4.10 in solc-bin was built ... - GitHub
Linux binary for version 0.4.10 in solc-bin was built from a different commit than binaries for other platforms #10839.
Read more >Solidity Version Management — py-solc-x 1.1.1 documentation
Return the version of the current active solc binary, as a Version object. with_commit_hash : If True , the returned version includes the...
Read more >Set specific compiler version in truffle but still get "Source file ...
js, I set a specific compiler version: compilers: { solc: { version: "0.7.6", // Fetch exact version from solc-bin (default: truffle's version) ...
Read more >ParserError: Source file requires different compiler version
The solution to the error is // SPDX-License-Identifier: MIT pragma solidity >=0.6.0 <0.9.0;. Use this instead, hope this helps.
Read more >Compiler version not recognized - Tools & Infrastructure
in Visual Studio a balloon come up which says. Source file requires different compiler version (current compiler is 0.8.6+commit.11564f7e.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It should be due to the old one. Github uses 7 characters, but I think we’ve settled on 8 as it is less weird.
This is very old code. My guess would be that the date is part of the version string and thus the binaries are different, but we did not have a very reproducible build system back in the days anyway.