Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    "I think that's the 32-bit version." uname tell you the architecture of the kernel. That actually isn't what is important, except that to run a 64-bit userland you need a 64-bit kernel -- but running a 64-bit kernel doesn't make it so, because you can also run a 32-bit userland that way. Which is what the stock Raspbian/RpiOS is; 32-bit, although on some models it loads a 64-bit kernel by default. To build or use 64-bit software, you need a 64-bit kernel and a 64-bit userland. Commented Aug 26, 2021 at 13:52
  • 1
    "I must have installed the 64-bit version earlier which led to the problem. I still don't understand why it happened though and how I could build a 64-bit version of Ruby on that system configuration." -> Perhaps you typo'd 64 and 32 backward here but again: To build 64-bit software you need a 64-bit userland. It is not possible otherwise. Commented Aug 26, 2021 at 13:54
  • I’ll go back and try to install a 64 bit version of kernel and userland. Commented Aug 27, 2021 at 11:52
  • 1
    I had the same problem: 64 bits kernel loaded on a 32 bits userland. Checking my /boot/config.txt configuration I had the arm_64bit=1 option. By commenting it, I was able to reboot under a 32 bits kernel and the compilation went well. Commented Sep 13, 2022 at 13:44