Merged
Conversation
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
I found a build issue with libxml2 2.14 above.
Summary
extconf.rbusesxmlXPtrNewRangeas a probe function to detect the presence of libxml2. This function was removed in libxml2 2.14.0 (March 2025) as part of the XPointer range/point extension cleanup, causing the library detection to fail and the gem build to abort with:This affects all systems with libxml2 >= 2.14.0, including Debian forky (testing, which ships libxml2 2.15.x).
Fix
Replace the probe function with
xmlXPtrNewContext, which remains in libxml2's XPointer API. The function is not used in the gem's C source code itself — it is only referenced inextconf.rbfor library detection.References