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
It's a known issue that the current implementation of lre-cc doesn't support cross compilation. This was ok for most usecases since it still worked in host == exec scenarios.
Now, upstream nix has marked our practice of using the wrapped clang (customClang) as faulty because the rust context is a cross compilation context but customClang in it's current state is not a cross compiler (NixOS/nixpkgs#323869). That is, the fact that our current implementation works should be treated as "working by chance".
To fix this we need to construct the LRE cc_toolchain properly as a cross compilation toolchain. This will also unlock arbitrary crosscompilation for C++ and Rust.
The text was updated successfully, but these errors were encountered:
It's a known issue that the current implementation of
lre-cc
doesn't support cross compilation. This was ok for most usecases since it still worked inhost == exec
scenarios.Now, upstream nix has marked our practice of using the wrapped clang (
customClang
) as faulty because the rust context is a cross compilation context butcustomClang
in it's current state is not a cross compiler (NixOS/nixpkgs#323869). That is, the fact that our current implementation works should be treated as "working by chance".To fix this we need to construct the LRE
cc_toolchain
properly as a cross compilation toolchain. This will also unlock arbitrary crosscompilation for C++ and Rust.The text was updated successfully, but these errors were encountered: