Thanks!
mpich seems to work (although we lose fortran support when cross compiling). This also fixed its dependants:
cross.riscv64.osumbcross.riscv64.sonar- `cross.riscv…
I would like to keep the simple idea that either cross-compilation for a package works (for the pinned commit) and is maintained with cross=true or is broken (even if its is not).
I assume…
Not sure if your use case can be satisfied by rarias/jungle#211. If so, I would prefer generating a flake.nix on disk so we can go back to the same shell in the…
IIUC this is adding packages with cross = false (or not set). Not sure if we want to keep both crossSet and crossList the same. In that case, using canCrossCompile may be handy.
Damm, I tested ${foo:+ } on bash but wrote the wrong thing :D
The only thing I don't like that it leaves a trailing whitespace in the lists, but I think keeping things simple is better.
Should be fixed now