-
-
Notifications
You must be signed in to change notification settings - Fork 897
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
upstream remaining truffleruby patches #2491
Comments
Note to self re: truffle dev env: comment out rbenv init in .bashrc and launch a new shell |
I think I've now got an approach that works for completely disabling the patches when not building with system libraries, and allowing them to still be used by older version (oracle/truffleruby#2639 (comment)). |
@aardvark179 That's great! Can you tell me which of these patches is still needed so I can upstream them? (I imagine the varargs workarounds are still needed?) |
The patch changes have now been merged to master. Current versions of Nokogiri no longer require any patches unless being build against system libraries (where we can support |
OK, closing this for now. I'll take a look at the truffle CI job which is failing in interesting ways. |
PR to upstream all remaining patches: #2663 It's still a bit unclear to me if we should support using system libraries for nokogiri on truffleruby.
|
See #1882 and #2095 for previous threads.
Conversation also happening in slack at https://graalvm.slack.com/archives/CMY63522F/p1648917137877149
Nokogiri patches live in https://github.com/oracle/truffleruby/blob/master/lib/truffle/truffle/patches/nokogiri_patches.rb
This approach is brittle in the face of trivial changes in Nokogiri's C extension. For example, this patch has been broken since this commit renamed
thing
toretval
in Nokogiri v1.13.0. This is coming up again in #2489 where the code using variadic args is being modified and breaking more patchesOne option is to upstream all of those changes, which I think would be preferable because it's easier to see and reason about.
The text was updated successfully, but these errors were encountered: