You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gem fails to find a proper binary for my 32 bit Debian server.
The problem is that RbConfig::CONFIG['host_cpu'] reports i486, while uname -m gives me i686.
I guess that RbConfig::CONFIG['host_cpu'] reports the compile configuration of Ruby, not the actual platform. It also will report a 32 bit architecture if you run a 32 bit ruby binary on a 64 bit platform.
I'm not sure if there's a proper way to detect the architecture of the actual platform ruby is running on instead of what it was compiled for (https://github.com/rdp/os does not do this either). Of course one could invoke a shell and ask e. g. uname, but...
The easiest fix would be to install the i686 version of phantom even if RbConfig::CONFIG['host_cpu'] reports i486. The probability of running on an actual i486 or Pentium should be quite low. You could give a warning in that situation. Would be nicer than just giving up.
I can prepare a PR if we agree on a solution for this.
The text was updated successfully, but these errors were encountered:
The gem fails to find a proper binary for my 32 bit Debian server.
The problem is that RbConfig::CONFIG['host_cpu'] reports i486, while uname -m gives me i686.
I guess that RbConfig::CONFIG['host_cpu'] reports the compile configuration of Ruby, not the actual platform. It also will report a 32 bit architecture if you run a 32 bit ruby binary on a 64 bit platform.
I'm not sure if there's a proper way to detect the architecture of the actual platform ruby is running on instead of what it was compiled for (https://github.com/rdp/os does not do this either). Of course one could invoke a shell and ask e. g. uname, but...
The easiest fix would be to install the i686 version of phantom even if RbConfig::CONFIG['host_cpu'] reports i486. The probability of running on an actual i486 or Pentium should be quite low. You could give a warning in that situation. Would be nicer than just giving up.
I can prepare a PR if we agree on a solution for this.
The text was updated successfully, but these errors were encountered: