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
Is there a reason you only build GNURadio for linux-aarm64, but not for linux-arm?
Although many modern ARM devices, like Raspberry Pi's, are 64bit, many Linux distros are prinmarily supporting 32bit on them [1][2], so it would be really helpful to have a 32bit build to run GNURadio on them.
The text was updated successfully, but these errors were encountered:
Of course it's not just GNU Radio that would need to be built for 32-bit Linux ARM, but all of its dependencies as well. That means it really needs to be something that the conda-forge project supports, which it currently does not. I don't know for sure why it's not supported, but if I had to guess:
No easy access to native build hardware (might be slow anyway?), so emulation or cross-compilation is required. The infrastructure to do that came only a few years ago, so there's no momentum from when 32-bit ARM was more prevalent.
Not enough demand to make the effort (maintainer time and build time) worth it.
As you say, most modern ARM devices are 64-bit, and it's just the default operating system that is 32-bit. Users who really want it can replace the OS with a 64-bit one, then use the linux-aarch64 conda-forge packages.
Conda-forge is mostly a volunteer effort, and nobody has wanted to scratch that itch badly enough to make it happen.
Comment:
The way I read the build instructions you are using a Docker image that already contains QEMU for 32 and 64bit ARM.
Is there a reason you only build GNURadio for linux-aarm64, but not for linux-arm?
Although many modern ARM devices, like Raspberry Pi's, are 64bit, many Linux distros are prinmarily supporting 32bit on them [1] [2], so it would be really helpful to have a 32bit build to run GNURadio on them.
The text was updated successfully, but these errors were encountered: