-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
dyld: Symbol not found: ___CFObjCIsCollectable #45042
Comments
🤔 |
Hmm, I was expecting this to be the problem but that doesn't seem to be it. I was expecting our version not to have it while libsecurity is expecting it to be there.
|
Got access to macOS 10.13.6 and it works there, so, yes, a Mojave regression. |
EDITED: Nevermind that. I understand more about how all these libraries get instantiated, now. Also hitting this on the latest Mojave beta. |
Due to a suggestion at Line 636 in 7736337
cacert added to nativeBuildInputs to see if that gets things any further along. Will update if/when it finishes.
Update: No dice. Same |
I tried to follow the story here and I didn't see a resolution, so I assume this is still broken. I'm on the current bleeding master and trying to build
Darwin is greek to me, but from the previous commands, it looks like the symbol isn't copied or at least is undefined?
This would seem to line up with @LnL7's theory from #45042 (comment) |
@cransom For the immediate problem of
|
I think we should try using the impure Security framework for now. I looked at the issue and it's definitely not obvious what to do. Perhaps updating to the latest Apple open source release fixes it but just as likely could be something else. /cc @copumpkin @pikajude |
Unless Apple has a separate channel for alphas/betas, we have the latest version from https://opensource.apple.com/tarballs/libsecurity_utilities/ |
They’ve moved it all to security. Those are from like 10.9 |
@copumpkin @LnL7 any objections removing libsecurity_utlities in favor of impure Security? |
Is this unresolved as of now? This is my error (calling googleapis through wreq/http-client:
Strange that there is a "dyld symbol not found" error, and then "certificate has unknown CA". |
I opened #47676 to fix this (temporarily at least). |
@matthewbauer thank you for doing this! |
darwin.security_tool is currently broken in Mojave. See issue NixOS#45042 for more info. Our security_tool stuff comes from 10.9 so I suspect that it needs an update. Here I am putting in a hack to get things working again. This uses the system provided security binary at /usr/bin/security to avoid the issue in Haskell’s x509-system package. Unfortunately, this will break with the sandbox. I am also working on a proper fix, but this requires updating lots of Apple stuff (and also copumpkin’s new CF). You can follow the progress on this branch: https://github.com/matthewbauer/nixpkgs/tree/xcode-security This commit should be backported to release-18.03 and release-18.09. /cc @copumpkin @LnL7 @pikajude
darwin.security_tool is currently broken in Mojave. See issue #45042 for more info. Our security_tool stuff comes from 10.9 so I suspect that it needs an update. Here I am putting in a hack to get things working again. This uses the system provided security binary at /usr/bin/security to avoid the issue in Haskell’s x509-system package. Unfortunately, this will break with the sandbox. I am also working on a proper fix, but this requires updating lots of Apple stuff (and also copumpkin’s new CF). You can follow the progress on this branch: https://github.com/matthewbauer/nixpkgs/tree/xcode-security This commit should be backported to release-18.03 and release-18.09. /cc @copumpkin @LnL7 @pikajude
darwin.security_tool is currently broken in Mojave. See issue #45042 for more info. Our security_tool stuff comes from 10.9 so I suspect that it needs an update. Here I am putting in a hack to get things working again. This uses the system provided security binary at /usr/bin/security to avoid the issue in Haskell’s x509-system package. Unfortunately, this will break with the sandbox. I am also working on a proper fix, but this requires updating lots of Apple stuff (and also copumpkin’s new CF). You can follow the progress on this branch: https://github.com/matthewbauer/nixpkgs/tree/xcode-security This commit should be backported to release-18.03 and release-18.09. /cc @copumpkin @LnL7 @pikajude
@domenkozar no objections |
(triage) If I read it correctly, this is currently solved by #47676? |
Yeah as well as we can until we can update Security. |
This happens on macOS Mojave 10.14:
(the expected result is a 403.)
I am not sure if it is a Mojave-specific issue as I currently don’t have a previous version of macOS to test with, but I’ll ping #42719 just in case.
The text was updated successfully, but these errors were encountered: