luisfg30

> You can maybe try compiling one or both with the RUSTFLAGS described in https://github.com/rust-bitcoin/rust-secp256k1/tree/master/secp256k1-sys#linking-to-external-symbols Yes. So far I was trying to build all modules off this project to understand...

> Adding `--cfg=rust_secp_no_symbol_renaming` to `RUSTFLAGS` give undefined reference errors: > > https://github.com/brunoerg/bitcoinfuzz/actions/runs/13813902574/job/38641980908pr=91#step:16:47 Exactly, I tested it locally and got the same error

> I've encountered similar Rust and Go([#93](https://github.com/brunoerg/bitcoinfuzz/issues/93)) errors when setting up Dockerfiles and docker-compose for the project. To solve this, I'm considering merging related modules: combining Go-based ones like **lnd**...

> Isn't this library just `secp256k1-sys`? Exactly, actually the [repo](https://github.com/rust-bitcoin/rust-secp256k1/tree/master/secp256k1-sys) explains a very similar use case. But the two modules (rustbitcoin and rustminiscript) depends on this [crate](https://crates.io/crates/secp256k1), they have this...

Ack

It seems that when building multiple modules we start to have a problem of shared dependencies between them. For instance the rustbitcoin and rustminiscript had a name conflict on `rustsecp256k1`....