-
Notifications
You must be signed in to change notification settings - Fork 38
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
xft2-dev patch to complie under macOS 15 / CLT 16.1 #1169
base: master
Are you sure you want to change the base?
Conversation
Needed cast of NULL to (unsigned long) in xftdpy.c
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.
Does build on 14.7/Xcode 16.1 as well; however I was also able to build the latest version 2.3.8 without needing to patch any additional files; the bug in https://bugs.freedesktop.org/show_bug.cgi?id=47178 seems to have long been fixed upstream.
I will try the newer upstream version, I just didn't want to get into recreating a complex patch file. |
Updated to use upstream 2.3.8 version. Only tested on Intel 15.X system |
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 good apart from the Shlibs-version; built on 14.7/Xcode 16.1-arm64.
I originally tried with the old AM_CPPFLAGS
patch (the freetype one in xftglyphs.c
is already merged upstream), but that does not seem to be needed anymore either – compiled with -I../include/X11/Xft
in front in any case.
After reading the shlibs policy, I am not sure why this package would be compatibility version 6.0.0 vs 5.0.0 and not 2.0.0. What sets that version number? Is it just an incremented value as the shlib version is changed? Why would it be a major change instead of a minor change to reflect the actual code revision version? |
The compatibility version is whatever |
Is the spacing bug mentioned in the unpatched .info (now at https://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/1 ) fixed? @dmacks ETA: noticed @dhomeier saying https://bugs.freedesktop.org/show_bug.cgi?id=47178 was fixed. That bug was only closed because upstream moved from bugzilla to gitlab. The moved current bug URL is at my link above. |
Doesn't matter since I think the NULL fix is fine, but upstream changed it to I cherry picked the first commit (NULL fix) and applied it to master. |
I thought I had reverted everything except the NULL fix. But anyway, thanks, and I think which value is cast to what is irrelevant. I personally prefer keeping the NULL for readability of the code, but YMMV. |
Yeah, I don't care if it's a typed NULL or 0. Anyway, I have no idea why this PR shows conflicts since I specifically cherry picked the first commit in the PR. |
I see the difference, the update to the newer upstream as suggested by dhomeier was rejected. 2.3.8 vs 2.3.0 |
Been traveling, seems like I didn't push the reversion to the previous Shlibs def. Now done. |
From the build output during deb file validation at the end:
The values before 928321f were actually correct. |
The previous ones were those for 2.3.8, these are now the 2.2.0 ones again, but I thought the update to 2.3.8 was rejected since it is not clear if the spacing problem in https://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/1 has really been fixed? |
# Conflicts: # 10.9-libcxx/stable/main/finkinfo/x11/xft2-dev.info # 10.9-libcxx/stable/main/finkinfo/x11/xft2-dev.patch
% otool -L /opt/sw/lib/xft2/lib/libXft.2.3.8.dylib /opt/sw/lib/xft2/lib/libXft.2.3.8.dylib: /opt/sw/lib/xft2/lib/libXft.2.dylib (compatibility version 6.0.0, current version 6.8.0)
Set compatibility version to 6.0.0 as tool declares it % otool -L /opt/sw/lib/xft2/lib/libXft.2.3.8.dylib |
Needed cast of NULL to (unsigned long) in xftdpy.c to comply with stricter compiler requirements.