-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Restore the ability to build with clang on linux #4129
Comments
I marked this as stale due to inactivity. → More info |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tweag-fellowship-fuzzing-nix-1/13904/1 |
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Fix #4129 /cc @Pamplemousse
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Likewise, `devShell.x86_64-linux.clang11StdenvPackages` is a development shell for Nix with clang11 Fix #4129 /cc @Pamplemousse
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Likewise, `devShell.x86_64-linux.clang11StdenvPackages` is a development shell for Nix with clang11 Fix #4129 /cc @Pamplemousse
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Likewise, `devShell.x86_64-linux.clang11StdenvPackages` is a development shell for Nix with clang11 Fix #4129 /cc @Pamplemousse
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Likewise, `devShell.x86_64-linux.clang11StdenvPackages` is a development shell for Nix with clang11 Fix #4129 /cc @Pamplemousse
@regnat would love to see this as a switch back + documentation in the Hacking Docs. I recently made local modifications to support Clang, that were fairly straightforward. I am not familiar enough with Flakes though to make it generic. Can flakes also add additional "build modes" ? |
For a (currently hardcoded and limited) list of stdenvs, make `.#$nix-${stdenvName}` correspond to a Nix built with the corresponding stdenv. For example, `.#nix-${clang11Stdenv}` is Nix built with clang11. Likewise, `devShell.x86_64-linux.clang11StdenvPackages` is a development shell for Nix with clang11 Fix #4129 /cc @Pamplemousse
Is your feature request related to a problem? Please describe.
Before the migration to a flake, the
shell.nix
file took auseClang
argument that allowed to easily useclangStdenv
rather than the default one. This argument doesn't exist anymore, and to the best of my knowledge, the only way to use clang is to patch theflake.nix
fileDescribe the solution you'd like
Restore a simple way to use clang rather than gcc for the build
Additional context
I guess adding back use
useClang
argument isn't possible (#3843 (comment)). Maybe it's possible to just add a new set of platforms (something likex86_64-linux-clang
and friends) to the flake, but I'm not aware of anything on the nixpkgs side to handle thatThe text was updated successfully, but these errors were encountered: