Open Schwartz10 opened 1 year ago
Hey @arajasek - i went ahead and just did the name remappings and things are working again on my end. A simple replace of https://github.com/ipsn/go-secp256k1 => https://github.com/glifio/go-secp256k1 v0.0.1 does the trick
@Kubuxu @magik6k thoughts?
Let’s try go-ethereum , keeping it to release versions not git commit.
It kind of looks like here that @Schwartz10 fixed this with the symbol renaming. Arugably #1 may be a little cleaner as it reduces the dependencies requirements by 1, but is this fixed? Is there a PR for Jon's fix?
Checklist
Latest release
, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Describe the Bug
Thanks @Stebalien for the help on articulating this issue:
ipsn/go-secp256k1
is a fork ofgo-ethereum/crypto
, which is used infilecoin-project/go-crypto
(filecoin-project/go-crypto go.mod)Because
ipsn/go-secp256k1
is a fork ofgo-ethereum/crypto
, it reuses the same C libraries, with the same symbols.The result is that importing both
go-ethereum/ethereum
andfilecoin-project/lotus
in the same go module causes build errors when running clang. I expect relying on these two modules will be a not-so-uncommon use case among early FEVM builders, since there's helpful APIs in both.Steb had two ideas:
Logging Information