-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Building reth-primitives
fails when consuming reth
as a library target
#8713
Comments
Propagating the patch locally (by copying it into the |
yeah, we currently use a revm patch, see Lines 459 to 463 in 40fc19f
we'll get rid of this with a new revm release |
This should be fixed prior to 1.0. Given that we're already at a release candidate and that no such |
an empty project only with this fails :-( [dependencies] [patch.crates-io] |
@undenuicap we will remove the patches soon, in the meantime please use this revision (from Cargo.toml) [patch.crates-io]
revm = { git = "https://github.com/bluealloy/revm.git", rev = "41e2f7f" }
revm-interpreter = { git = "https://github.com/bluealloy/revm.git", rev = "41e2f7f" }
revm-precompile = { git = "https://github.com/bluealloy/revm.git", rev = "41e2f7f" }
revm-primitives = { git = "https://github.com/bluealloy/revm.git", rev = "41e2f7f" } |
Describe the bug
In bluealloy/revm#1143, the signature for
validate_initial_tx_gas
was changed to accept an additional parameter for the EOF initcodes. As of Reth 0.2.0-beta.9, when calculating intrinsic gas usage of a transaction, the pre-EOF interface is used (i.e., only four parameters are provided tovalidate_initial_tx_gas
).reth/crates/primitives/src/revm/compat.rs
Lines 28 to 40 in 7b435e0
To achieve this, Reth patches the various
revm-*
crates:reth/Cargo.toml
Lines 453 to 457 in 7b435e0
When building
reth-primitives
directly, viacargo build -p reth-primitives
, this works; however, breaks when relying on Reth as an upstream dependency as Git-based dependencies cannot be transitively patched.This is fixed by not hiding Reth's dependency on a specific commit by patching:
Steps to reproduce
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
0.2.0-beta.9 (
7b435e0
)What database version are you on?
N/A
Which chain / network are you on?
N/A
What type of node are you running?
Archive (default)
What prune config do you use, if any?
N/A
If you've built Reth from source, provide the full command you used
cargo run
Code of Conduct
The text was updated successfully, but these errors were encountered: