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
rtags: link to libclang.dylib at absolute path on darwin #25309
Conversation
@acowley, thanks for your PR! By analyzing the history of the files in this pull request, we identified @anderspapitto, @periklis and @copumpkin to be potential reviewers. |
I noticed similar behaviour with #25352, not sure if there's a reason for it but that's set in the library id of libclang.
|
I don't have any strong feelings regarding fixing it here or there. This is where it bit me, but changing the clang derivation is fine by me. I have another PR open to add something to |
Relevant: #21624 |
Previous versions of libclang have an absolute path for the library id, so I don't expect any issues if we rewrite it. I'm testing the clang changes to see if that fixes the problem. |
@domenkozar: fixDarwinDylibNames doesn't seem to fix this because the problem is in linking the binaries incorrectly. It looks like rtags is doing something weird with CMake changing rtags in weird ways. Either way this patch does fix rtags for me while fixDarwinDylibNames doesn't change anything. |
@matthewbauer the This commit LnL7@972631c fixes the issue, but the clang builds keep timing out 😕 http://hydra.nixos.org/eval/1358432. I would prefer to make sure everything looks good before pushing that to staging. |
@LnL7 This is dragging out a bit. If there isn't much of a hue and cry around nixpkgs due to the |
Agreed, I didn't expect testing my changes to stall this long. This is also not a problem when lib clang is fixed, it just becomes a noop. |
Motivation for this change
I encountered a runtime link failure without this change. Perhaps the executables could be left using
@rpath
in conjunction with some other configuration, but I am not sure what the advantage to that arrangement is versus linking to thelibclang
in scope at build time.Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)