Closed michaelpj closed 6 months ago
It's also not easy to avoid this dependency, since it's a transitive dependency of criterion
.
Hmm, apparently the symbol has been private for a long time? https://github.com/baldurk/renderdoc/issues/365
Maybe you just have to link against libgcc?
Okay, I tried forcing gcc into pakcages.bitvec.library.libs
and it didn't help. I'm just going to leave this for someone who has a better idea what is going on.
Ah of course: cardano-node
sets -fexternal-interpreter
for plutus-core
to work around a different weird issue we had. So perhaps this only appears if you're using the external interpreter.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bitvec-1.1.5.0
now has asimd
flag (on by default) which tries to use SIMD operations for things. The implementation of this apparently does some probing for CPU features. I think this is just not available in the Nix sandbox, since we get errors like this:Then again, these are also from
ghc-iserv
, so this might only manifest when there are TH splices involved. I'm not 100% sure, but turning off thesimd
flag fixes it.Reproducible on
cardano-node
if you bump the index state to allow the newerbitvec
and turn thesimd
flag on.