-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
python312Packages.cffi: remove unnecessary Darwin patch (attempt 2) #382404
Conversation
It doesn’t appear to do anything on Darwin, so drop it.
This header contains availability annotations for libffi functions, which some packages (such as Python’s) check to determine whether they are building against Apple’s libffi fork.
…ch"" This reverts commit 340c3f6.
1026639
to
741de2b
Compare
I dropped the commit to build I also checked the segments on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Feel free to merge if you verified the python3Packages.cffi
build.
# Make sure Apple’s header with availability annotations is installed in place of the generated one. | ||
# Use `macCatalyst` instead of `iosmac` to avoid errors due to invalid availability annotations. | ||
substitute darwin/include/ffi.h "$dev/include/ffi.h" --replace-fail iosmac macCatalyst |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, is this an internal SDK difference or a bootstrap tools thing or what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The header that Apple ships uses macCatalyst
, but the one in the source release uses iosmac
. I assume they do some sort of post-processing when they build the SDK.
This PR updates the build of darwin.libffi to more closely match the way the system library is built, which should allow the Python cffi patch to be dropped.
Pinging @emilazy who worked on the previous attempt to drop it and @patryk4815 who reported #380786 (which is now closed, but that issue prompted the work on this PR). It would be good to know whether (the previous version of?) unicorn still exhibits the reported issue.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.