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
32-bit Raspberry Pi OS runs with a 64-bit kernel and 32-bit userspace. This means that opam var arch returns arm64, but since the C compiler is 32-bit, it would be much more helpful it returned arm32 (as it does if run through linux32).
Certainly for Raspberry Pi OS, but possibly in general on Unix, we could perhaps use uname -m to determine the machine architecture, but then refine it with getconf LONG_BIT and if that returns 32 then map a few of the architectures down to smaller userspaces?
The text was updated successfully, but these errors were encountered:
I'm also wondering instead whether we could have a new global variable indicating the result of getconf LONG_BIT or some such to keep arch really referring to the kernel architecture, but expose the ability to know what the C compiler is likely to be doing.
32-bit Raspberry Pi OS runs with a 64-bit kernel and 32-bit userspace. This means that
opam var arch
returnsarm64
, but since the C compiler is 32-bit, it would be much more helpful it returnedarm32
(as it does if run throughlinux32
).Certainly for Raspberry Pi OS, but possibly in general on Unix, we could perhaps use
uname -m
to determine the machine architecture, but then refine it withgetconf LONG_BIT
and if that returns32
then map a few of the architectures down to smaller userspaces?The text was updated successfully, but these errors were encountered: