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
google-chrome, treewide: fix patchelf usages to not crash constantly, patchelf as native #47444
google-chrome, treewide: fix patchelf usages to not crash constantly, patchelf as native #47444
Conversation
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: google-chrome, virtualbox Partial log (click to expand)
|
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: google-chrome, virtualbox Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: virtualbox The following builds were skipped because they don't evaluate on x86_64-linux: google-chrome Partial log (click to expand)
|
I haven't looked at the details yet, but for virtualbox it might be easier to override stdenv in all-packages.nix to replace patchelf with patchelfUnstable. Similar to overrideCC ...
|
Current/previous behavior is the patchelf process aborting after a somewhat unfriendly message about an assertion failure.
In a few cases it wasn't clear so I left them as-is. While visiting these moved other things to nativeBuildInputs when it was clear they were one of these cases: * makeWrapper * archive utilities (in order to unpack src) * a few of these might no longer be needed but leaving for another day
d3a465d
to
eb91037
Compare
Bah, I'll just drop the virtualbox fix -- although I do still move it to nativeBuildInputs since that's where it should be as long as it's anywhere. Then we can use your PR to remove it and leave fixing it for another day (another PR) since it appears to be more involved than I originally thought :). |
No attempt on x86_64-linux (full log) The following builds were skipped because they don't evaluate on x86_64-linux: google-chrome Partial log (click to expand)
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: google-chrome Partial log (click to expand)
|
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: google-chrome Partial log (click to expand)
|
@GrahamcOfBorg build virtualbox |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: virtualbox Partial log (click to expand)
|
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: virtualbox Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: virtualbox Partial log (click to expand)
|
Thanks for working with me on this! |
Great stuff! |
Tired of seeing build logs telling me patchelf segfaults 20 times or
unfriendly assertion failure messages, neither of which are reasonable state of "normal".
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)Tested virtualbox, google-chrome, and a number of the expressions modified but not all.