search

sparklemotion / nokogiri.org

Documentation site for Nokogiri (a ruby library)
https://nokogiri.org/
MIT License
45 stars 24 forks source link

Update Termux installation document #47

Closed ajpalok closed 2 years ago

ajpalok commented 2 years ago

Update Termux installation document to prevent following issue of https://github.com/sparklemotion/nokogiri/issues/2416

flavorjones commented 2 years ago

Hi! Thank you for submitting this pull request.

This change implies that it's not possible to run precompiled binaries on Termux. Is that your intention? Is that true? If so, that's a pretty important point that we should state clearly, and potentially link to some documentation.

I want to go back to your original bug report, where I asked you for help reproducing what you're seeing. I am asking again: how can I most easily get a Termux environment running to explore? Can you help me to understand what's going on here?

flavorjones commented 2 years ago

This page:

https://wiki.termux.com/wiki/Differences_from_Linux

says, in part:

Dynamically linked programs will not run because the linker is expected in a nonexistent location (/lib) and libc ABI does not match

This, I guess makes sense.

I've finally got a termux docker container running (thanks to https://github.com/termux/termux-docker) and I see that gem env says, in part:

  - RUBYGEMS PLATFORMS:
     - ruby
     - x86-linux-android

This, again, would have helped me -- in your original ticket! -- to understand what's happening.

flavorjones commented 2 years ago

I'm going to close this and will rewrite the Termux section. Thanks again for calling my attention to this problem.

flavorjones commented 2 years ago

See fc8c33d and https://nokogiri.org/tutorials/installing_nokogiri.html#termux

ajpalok commented 2 years ago

Thanks for the huge support. Mainly my bundler was consistently installing the precompiled native gem as the bundler platform was set to the aarch64-linux and today I got the point (which I totally forgot to check at that moment while debugging the issue) and also got that by editing the platform from aarch64-linux to ruby, makes everything ok to avoid installing the precompiled native gem. Again, Thanks for the huge support @flavorjones. --EDITED-- I guess a last issue found after the documentation update which I got while testing on my device and I've added the issue in my main bug report. I guess that will fix others problems too in future and also will help to make the documentation more enriched too.