Skip to content

Make binutils in ruby language integration even lower priority - #389

Open
chvp wants to merge 1 commit into
numtide:mainfrom
chvp:fix/lowprio-conflict
Open

chvp wants to merge 1 commit into
numtide:mainfrom
chvp:fix/lowprio-conflict

Conversation

@chvp

@chvp chvp commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Because gcc is lowPrio by default this lowPrio call didn't actually avoid conflicts in ruby shells. By setting the binutils priority even lower, we can make it so the shell still builds. Somehow this was only a problem on macOS, not sure why, but this at least fixes it.

Fixes #380.

Because gcc is [lowPrio by
default](https://github.com/NixOS/nixpkgs/blob/93cdf2419ff36df3163d111fc65ff04fa5ccc67c/pkgs/development/compilers/gcc/all.nix#L25)
this lowPrio call didn't actually avoid conflicts in ruby shells. By setting the
binutils priority even lower, we can make it so the shell still builds.
@chvp chvp changed the title Make binutils in ruby language even lower priority Make binutils in ruby language integration even lower priority Nov 7, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Collision between gcc and binutils despite lib.lowPrio on aarch64-darwin

1 participant