Issue description
Our CC wrapper doesn't wrap all the binaries that GCC provides -- namely prefixed with architecture x86_64-unknown-gnu-gcc and variations. Because unwrapped GCC is propagated to user environments from the wrapper it ends up in the path (for example in FHS environments). One example of problem that it causes is that OpenWrt picks it up and fails to compile.
wrapCC needs to detect and wrap those.
Steps to reproduce
buildEnv { paths = [ gcc ]; } (you can also add it to environment.systemPackages or buildFHSUserEnv);
- Try to compile something with
x86_64-unknown-gnu-gcc (prefix may vary).
Technical details
- Nixpkgs version: (run
nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) 59dbcef
Issue description
Our CC wrapper doesn't wrap all the binaries that GCC provides -- namely prefixed with architecture
x86_64-unknown-gnu-gccand variations. Because unwrapped GCC is propagated to user environments from the wrapper it ends up in the path (for example in FHS environments). One example of problem that it causes is that OpenWrt picks it up and fails to compile.wrapCCneeds to detect and wrap those.Steps to reproduce
buildEnv { paths = [ gcc ]; }(you can also add it toenvironment.systemPackagesorbuildFHSUserEnv);x86_64-unknown-gnu-gcc(prefix may vary).Technical details
nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) 59dbcef