fix evmone version #296
Draft
fix evmone version #296
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: eolesinski <[email protected]>
eolesinski
force-pushed
the
fix-evmone-version
branch
from
0aae731
to
aa5b80f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #275 by pinning the installation to a specific version.
Both EVMONE and EVMC are upgraded to "Cancun" versions 0.11.0 and 11.0.1 respectively. This upgrade prevents an error where EVMONE fails to build and the Hunter install subsequently gets stuck when running the
setup-dependencies.shon a MacBook M3 Max running Sonoma 14.5.Tested: tested by running
./scripts/setup-dependencies.shand verified that the Hunter install does not hang.