You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
wasm2c from binaryen conflicts with wasm2c from wabt #9002
The newly added (#8763) wasm2c tool introduces a conflict with wabt's wasm2c, which would prevent both packages from being installed at the same time on Fedora (and I have another package that requires both to build).
Are these two wasm2c supposed to be drop-in replacements and compatible? If not, can you rename one of them?
sharing what I am doing, this is for people who are using the classically controversial command sudo make install or logical equivalents to or approximations of it, so that their wabtwasm2c does not get erased.
Since Binaryen's wasm2c is still very much under construction, it might also make sense to make building it opt-in in the cmake config. I would be happy to accept a PR making that change.
Activity
kripken commentedon Aug 13, 2026
cc @lexi-nadia @tlively
There is some ongoing debate about the future of these tools, so maybe this is moot or will be.
But isn't the usual practice to rename on the distro side? (e.g.
binaryen-wasm2corbyn-wasm2cfor the fedora package)rathann commentedon Aug 13, 2026
Alright, thanks for your consideration.
It is and I'm going to do that. For now, I'm more concerned that at least one
littest fails on i686, but I'll open a separate issue for that.robertkirkman commentedon Aug 18, 2026
sharing what I am doing, this is for people who are using the classically controversial command
sudo make installor logical equivalents to or approximations of it, so that theirwabtwasm2cdoes not get erased.tlively commentedon Aug 18, 2026
Since Binaryen's wasm2c is still very much under construction, it might also make sense to make building it opt-in in the cmake config. I would be happy to accept a PR making that change.