Closed ghost closed 3 months ago
I was able to compile it locally without yay
Interesting to see that the error seems to be lying in one of the dependencies that seem to build some assembly code, which is then used via C language FFI. Since building locally helped, I would guess there is some cache stuff going on that could potentially be fixed with cargo clean
/removing the package cache altogether. Anyways, glad to see the problem has been resolved for now.
tried both packages. getting same error.