I have raspberrypi4.
Current official Raspberry OS is 32-bit a.k.a armhf(armv7l).
I have some issues installing packages or using docker images and I think it is related to 32-bit system.
It seems like ARM architecture has less binaries compatible than x86. And 32-bit armhf is even worse.
So, what I'm curious about is...
would installing 64-bit version of OS help some compatibility issues with packages? I mean like there are few apt PPAs supports 32-bit. Will I be able to use more PPAs and install latest packages with 64-bit OS?
Any suggestion or guess is welcome.
Yes, arm64 is a better choice for wider compatibility with available docker images. arm64 images are also able to use more than 4GB process memory.
As of 22 February 2022 on hub.docker.com:
123,643 ARM64 images
69,567 ARM images
Update December 2022: With increased adoption of ARM64 in the Cloud (AWS Graviton, Azure Dpsv5, GCloud T2A) I expect ARM64 usage to continue to grow faster.
Related
I have a working debian package that I'd like to backport to the current version of Raspberry Pi OS 64 bit (not 32-bit Raspbian).
Confusingly, while Debian itself seems to be robust about enabling cross-builds in their own package, there seems to be much less official documentation about how raspberry Pi OS (64 bit) packages are built¹.
Since I'm relatively certain this should be possible, I ask:
How to take a debian .dsc / debian rules, and build, on an x86_64, a 64 bit Raspberry Pi OS 64-bit compatible image
without using QEMU to actually build the image on arm64, without access to an actual RPi,
using an existing debian package that is known to work on sid on aarch64, and should be backportable,
making sure it's actually built against the correct set of Raspbian dependencies.
I'm guess this is a rather standard thing, I just don't know how to do it. I'm happy with using containers and similar technology, as I can easily integrate that with CI.
I do not plan to use an Arm64 VM, as the software in question takes about an hour to build and test, on an x86_64 server, natively.
¹I've talked to plugwash of Raspbian fame, and as earlier versions of this question showed: there's significant confusion about the heredity of Raspbian OS 64 bit: It's not Raspbian nor based on it. But people including Wikipedia and the RPi Foundation themselves conflate Raspberry Pi OS and Raspbian ("Raspberry Pi OS, formerly Raspbian"), which is 32 bit only.
RaspberryPi documentation here has explained how to build the x64 kernel from the source. What you want is in a way exactly like that.
Notice this line on the Kernel building page:
sudo apt install crossbuild-essential-arm64
This command on your Linux host machine installs a compiler that runs on an AMD64 machine but produces a binary that runs on an ARM machine.
And this line tells the compiler to actually build the source for that architecture:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- Image modules dtbs
Image modules dtbs are specific to your project. they may differ.
As for your Debian package, there is no way that you can transform an AMD64 package into an ARM one. Your package for the RaspberryPi if doesn't exist in an official or some third-party repository, must be built from the source.
Find the source code of your package and build it very similarly to RaspberryOS.
If your Package has dependencies it gets a little more complicated. First, install the dependency on your RaspberryPi. Then you should set up a sysroot on your host machine which is basically a mirror image of the preinstalled packages on RaspberryPi. Then for compiling your package you should give the sysroot address to cross compiler so that it can find dependencies.
There is another way too, you can put the source code of your package on your RaspberryPi and build it locally which can take a very long time based on the source code. Just to have a sense, Qt source code without WebEngine module took 48h for me. But Qt is big.
In conclusion, if your package binary is not on any repository you must compile it from the source.
Cross-compilation of different projects and executables are very similar to each other. To have a clear understanding of the process it can be beneficial to look for some other projects that were ported to RaspberryPi OS. Things like Qt, TagLib for android, and ...
First, I would take a look here:
https://github.com/Truelite/qt5custom for inspiration. I checked and those scritps work. However, you might have problems going completely „qemuless”; e.g. in case of QT some libraries needed to be added to host machine sysroot and qemu was simply the easiest way to add them properly: it seems to me that multiarch Debian has some deficiencies in the field of cross-compilation and the simplest way to overcome them is to pretend it’s the native one.
Because the documentation recommends Ubuntu 15.10 as a yocto build host, we went to considerable effort to set this up, only to find that Bitbake still tells us that this is not a supported version.
What is the latest recommended Ubuntu version, please? I'm thinking we may as go with the latest LTS.
If you use Warrior Yocto version, you can use Ubuntu 18.04 as stated here. For older Yocto version, you'll need an older host distribution due to GCC support.
Anyway, I suggest you to build Yocto within a Docker environment, for example this one.
https://code.visualstudio.com/
It lists deb and rpm but the deb is for amd64
The reason it's called amd64 is simply that AMD beat Intel to market with the first 64-bit x86-compatible CPU, and therefore their version (which actually just extended the old x86 instruction set with new 64-bit variants) became the standard. You can most certainly use that version no matter what vendor your CPU is from as long as it supports x86 with 64-bit extensions.
Intel also tried with their own new architecture called Itanium (IA64), but that never really got enough traction (I don't think they ever made more than one generation of those chips?).
EDIT I see you're running 32-bit Linux, so you should get the 32-bit .deb version
What are the system requirements for vscode?
The download page only shows the different platforms this is available on, but doesn't mention any requirements such as Windows version (i know it doesn't work on XP) or additional required components, such as the .NET framework.
System requirements for VSCode are available on the documentation page.
In a nutshell, VSCode now is self contained for Linux, Mac and Windows. There is a complete list for the additional helpful tools available on the setup page.
It's not listed in their requirements, but you'll also need a decent video card. It may seem ridiculous, since it's mainly displaying text, but vscode's GPU hardware requirement is well beyond what other applications require. There is a switch --disable-gpu to switch it to software rendering but it's still laggy.
As of Version 1.32
1.6 GHz or faster processor with 1 GB RAM recommended
OS X Yosemite
Windows 7 (with .NET Framework 4.5.2), 8.0, 8.1 and 10 (32-bit and 64-bit)
Linux with GLIBCXX version 3.4.15 or later, GLIBC version 2.15 or later, tested with Linux (Debian): Ubuntu Desktop 14.04, Debian 7, Linux (Red Hat): Red Hat Enterprise Linux 7, CentOS 7, Fedora 23
I recently built a web application which needs to run bcrypt and mongodb over a raspberry pi 4 model b.
Mongodb require a 64 bit OS.
Bcrypt succeed installation only with 32 bit OS.
I used Ubuntu 20.04 for 64 bit OS and the latest version of raspbian 32 bit.
I searched in the npm bcrypt package documentation and I found out that they only support pre-built binaries for:
Windows x32 and x64
Linux x64 (GlibC targets only). Pre-built binaries for MUSL targets
such as Apline Linux are not available.
macOS
Therefore, I have those options:
Find another package (bcrypt like) which is functionnal for 64 raspberry pi's os
Find a way to install bcrypt on armv7l 64 bit OS
Downgrade mongo with an old version who support 32 bits and use Raspbian
I documented compiled all the logs in this post.
I'm sure someone already faced this issue and knows how to deal with this. Or even, if you know another alternative, I'll be glad to hear! Thank you