-
-
Notifications
You must be signed in to change notification settings - Fork 905
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
fix build error for nokogiri in loongarch64 #2831
Conversation
@zhangwenlong8911 Thank you for submitting this PR! Can you help me understand what the problem is that you're trying to solve? I don't think you need to update If you do want to precompile or cross-compile for loongarch64, let's have that conversation in a new issue, and let this PR be just for compiling from source. For compiIing from source, I believe fixing the libxml2/libxslt config files is sufficient. However, I would very much prefer if that change was made upstream in libxml2 and libxslt. Have you reported this problem in an upstream issue? If it's not possible to fix upstream, I'm OK with patching those files here. However -- we are already patching libxslt with Finally: do you have any ideas on how we can test that this platform works properly with these changes? |
update config.guess and config.sub for libxml2 and libxslt form https://git.savannah.gnu.org/gitweb/?p=config.git;a=tree to fix build error for libxml2 and libxslt
Thanks for your suggestion, I have removed the modifications to rakelib/extensions.rake and updated config.guess and config.sub in libxslt with one patch, The latest upstream config.guess and config.sub already include support for arm64 and loongarch64 At present, there is no better way to test. This submission is directly obtained from the upstream config project, and no other modifications have been made. At the same time, I have compiled aarch64 and loongarch64 locally. |
For future readers, I've verified that post-patch
(the files in the root directory are downloaded directly from gnu.org). Kicking off CI! |
Did this get reported upstream? That seems preferable to maintaining a patch file. |
@stevecheckoway I agree, upstream is the long-term fix. I asked for it to be reported upstream, not sure if it has (probably not). If memory serves (I wasn't able to find an example quickly, though), complaints about using old autoconf files have been deprioritized because you can "just run autoreconf", and at times a commitment was made to do better in the next release. The config.guess and config.sub files are added by the human packager of the tarball and are not under source control, which means that the versions used have varied quite a bit over time. The reality is that we've had to maintain a patch for libxslt for arm64 support since April 2021 so this isn't the worst thing in the world. Part of me actually wants to update mini_portile2 to inject the latest autoconf files if it can, but I'm not sure if that would break some projects, or be allowed by the respective licenses. |
@stevecheckoway @flavorjones |
Merged! Thank you, @zhangwenlong8911. This will be in the next release. |
update config.guess and config.sub for libxml2 and libxslt form https://git.savannah.gnu.org/gitweb/?p=config.git;a=tree to fix build error for libxml2 and libxslt