Installing the dependencies on the Pi
Pieter PTable of Contents list
OS installation and network configuration
If you haven't set up your Pi yet, follow the instructions on how to do so for Ubuntu or for Raspbian.
Make sure that you have the following set up correctly:
- A working network connection to the same local network as your computer.
- The hostname and DNS or mDNS configured correctly so you can find the Pi on the network as
e.g.
rpi3.local
, even if its IP address changes. - An SSH configuration on your computer so you can SSH into the Pi using e.g.
ssh RPi3
. - An SSH key from your computer installed in the
authorized_keys
of the Pi so you can SSH into it without having to enter your password each time.
Installation of the staging area
We now have to install all libraries and tools that were cross-compiled in the previous steps to the Pi.
This is as easy as just copying over the archive containing the staging area, and then extracting it to
the root directory.
All files in the staging area are either in /usr/local
or in /opt
,
so it won't interfere with software you installed through the package manager.
# Copy the staging area archive to the Pi
# This command may take a while, depending on the speed of your SD card
scp ./docker-arm-cross-build-scripts/staging-aarch64-rpi3-linux-gnu.tar RPi3:/tmp
# Install everything to the root of the filesystem
# (will only install to /usr/local and /opt)
# Enter the sudo password of the Pi if necessary
# This command may take a while, depending on the speed of your SD card
ssh -t RPi3 "sudo tar xf /tmp/staging-aarch64-rpi3-linux-gnu.tar \
-C / --strip-components=1 --keep-directory-symlink \
--no-same-owner --no-same-permissions --no-overwrite-dir"
# Configure dynamic linker run-time bindings so newly installed libraries
# are found by the linker
# Enter the sudo password of the Pi if necessary
ssh -t RPi3 "sudo ldconfig"
For the options used with the tar
command, you can consult the manpage, they're not that important.
The important thing is that files in the archive are extracted to the root of the filesystem,
e.g. if the archive contains a file
staging-aarch64-rpi3-linux-gnu.tar:RPi-Staging/usr/local/bin/python3.10
,
it will be extracted to /usr/local/bin/python3.10
.
To verify that the installation was successful, you can try running the newly installed Python interpreter: