-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
libffi: Add 3.4.6, remove 3.4.2 and 3.4.3 #23362
Conversation
🤖 Beep Boop! This pull request is making changes to 'recipes/libffi//'. 👋 @Hopobcn you might be interested. 😉 |
This comment has been minimized.
This comment has been minimized.
@uilianries @RubenRBS Do you think it's about time to remove pre-3.4.4 versions? 3.4.4 is used everywhere (except llvm-core which is still on 3.3, but is being updated in #22997), and is already about two years old, I don't think we need anything older. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Thanks a lot for the detailed PR body, it's super appreciated :)
@RubenRBS What do you think about removing the older versions? Only 3.3 is used, and it's by llvm-core, which is getting updated in another PR. 3.4.4 itself has been out for nearly 2 years, I don't think we need anything older. |
@Ahajha you could remove |
@uilianries I've removed those two versions. I realize my comment wasn't clear, 3.4.4 I think should stay for now (and would have to anyways), 3.3 was the other version that I think should be removed, but I'll wait until the llvm-core PR is merged to do that. |
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Uilian Ries <uilianries@gmail.com>
Conan v1 pipeline ✔️All green in build 10 (
Conan v2 pipeline ✔️
All green in build 10 ( |
@uilianries Thanks, was a bit tired last night :) |
Thank you for contributing!!!! 👏 |
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.
LGTM
"3.3": | ||
url: "https://github.com/libffi/libffi/releases/download/v3.3/libffi-3.3.tar.gz" | ||
sha256: "72fba7922703ddfa7a028d513ac15a85c8d54c8d67f55fa5a4802885dc652056" | ||
patches: | ||
"3.4.6": | ||
- patch_file: "patches/0002-3.4.6-fix-libtool-path.patch" |
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.
Please start adding patch_description
and patch_type
. Additionally patch_source
if applicable
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.
These were from existing patches, but I can do some digging and figure out their purposes.
Specify library name and version: libffi/3.4.6
The patch
0007-3.4.3-forward-declare-open_temp_exec_file.patch
(and friends) is no longer needed for the new version, as it has been upstreamed.The MSVC build changed slightly: libffi/libffi@2b2f61f, essentially there's a new
FFI_STATIC_BUILD
that replacesFFI_BUILDING
.I'm not certain that the
FFI_BUILDING
/FFI_STATIC_BUILD
macros need to be in the package info for non-MSVC builds. I've kept them for now, but maybe we could revisit at some point.Older versions of libffi don't support Apple ARM CPUs, it looks like there was an attempt to backport the fix, but the patch itself wasn't actually merged: #5085. There are plenty of newer versions so I don't think it's worth fixing at this point. Unsure why this was still an issue.