-
-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
binutils conflicts with itself (due to .dev output) #18839
Comments
Is that an old nix? I think the newer ones have the logic to install only relevant outputs. I don't know if that code is only on master though. |
It's the default Nix on NixOS 16.09 (as of a couple of days old, c02b9b9):
|
Hm, damn. I guess the workaround in the meantime is to install |
@dezgeg: Does that work for you? I get
|
D'oh, I forgot that it doesn't actually work... |
Why does the dev output have binaries, those should only be in the |
It has a symlink |
A quick grep seems to indicate that the dev output is only used for headers |
I'll just throw it in, in case it's not obvious for someone — a nasty workaround is to put some symlinks into your
|
I somehow missed this. I believe the symlink is useless, especially now that we have |
Fixes NixOS#18839. I suspect I once added this just because of some deficiencies in an early development version of the multiple-output framework in stdenv.
Fixes NixOS#18839. I suspect I once added this just because of some deficiencies in an early development version of the multiple-output framework in stdenv. (cherry picked from commit e2e270d)
Issue description
So it cannot be installed:
Technical details
The text was updated successfully, but these errors were encountered: