-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cc-wrappers should unconditionally provide target prefixed tools ${target}-gcc to shadow unwrapped bianries. #178802
Labels
0.kind: bug
Something is broken
Comments
/cc @Ericson2314 |
10 tasks
I'll ignore here our current sets of files typically present in various packages and their wrappers (picking a simple example):
For simplest cases we can wrap not just |
13 tasks
Proposed fix as #181724. Fixes at least |
trofi
added a commit
to trofi/nixpkgs
that referenced
this issue
Jul 16, 2022
In NixOS#87909 ("stdenv: always pass --build, --host to configure") we noticed that stdenv.cc exposes `c++` as a wrapped bianry and `x86_64-unknown-linux-gnu-c++` as unsrapped binary. As a result `x86_64-unknown-linux-gnu-c++` was not able to create basic bianries. This makes seepingly no-op `--host=x86_64-unknown-linux-gnu` option for `./configure` a breaking change. This change adds wrappers to prefixed binaries for cross and native cases where such an inconsistency exists. New validation change will catch new possible inconsistencies. It already caught existing inconsistencies in: `gcc`, `gfortran`, `gcj`, `gccgo`, `gdc`, `clang`. At least `radare2` build is fixed by consistent wrappers. It used to fail before as: radare2> ERROR: x86_64-unknown-linux-gnu-gcc cannot create executables Issue: NixOS#178802
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed the unwrapped binary leak in when built
enchant1
withconfig.configurePlatformsByDefault = true;
(pass--host=
for native builds). There linkage fails becauseCC=x86_64-unknown-linux-gnu-gcc
points to unwrapped binary:--host=${target}
effectively flips CC fromgcc-wrapper
togcc
. I'm surprised there is that little breakage. I'd saygcc-wrapper
should always provide bothgcc
(& co) and${target}-gcc
(& co).Proposal: install
${target}-gcc
for native wrappers along withgcc
.Optionally we can disable unprefixed tools as suggested by the TODO:
nixpkgs/pkgs/build-support/cc-wrapper/default.nix
Lines 37 to 40 in 7b185e0
The text was updated successfully, but these errors were encountered: