There was no /usr/lib/aarch64-linux-gnu - I checked when looking at toolchains to remedy this issue. So that seems to be the cause: I was not running a full 64bit kernel/OS/userland installation.
Thank you for clearing this up,
Michael
Read More...
I used Pi Imager to install "Raspberry Pi OS (Legacy, 64bit) a port of Debian Bullseye with security updates and desktop environment".
"uname -a" returned 'aarch64' (among other info). No further config was done on the system so I assumed that I was running a 64bit system.
Am currently trying installation with bookworm - usually I try to avoid OS-versions that are so young.
Thank you for responding,
Michael
Read More...
Hello Avocette,
thank you for the information that it cmpiles on bookworm which can also be gathered by watching Wolfgang's video some postings above. My question however was whether the scripts will work on bullseye.
Regards,
Michael
Read More...
Hi,
according to the documentation nou's scripts should work on any Debian-based distro. This would include Pi OS bullseye 64bit. However compilation on that distro fails repeatedly within the indi-3rdparty section at libahp-gt compilation/linking time. Error is "File format not recognized." for '/usr/lib/arm-linux-gnueabihf/libahp_gt.so' by ld. File is actually a 64bit object as expected.
Apologies for not supplying exact error messages - I am currently trying the same installation on Ubuntu 22.04 after it was mention within this thread and that seems to at least get over the indi-3rdparty section that breaks on Pi OS (but I would prefer to run the showle thing on Pi OS). If required I can set up the system again on a new SD card with Pi OS and supply exact info. But it can be reproduced quite easily.
Steps to reproduce: follow the installation instructions. Fresh install of Pi OS 64bit (desktop), get the scripts via git clone, run `./install-dependencies.sh` and run either "build-soft-stable.sh" or "build-soft-latest.sh" (it fails on either). Compilation runs fine till the indi-3rdparty section where the error occurs and the script stops.
Is this a known issue?
Is there anything that would need to be setup/configured/installed prior to cloing and running the scripts? I suspect that the gcc/cc/ld setup on Pi OS is different from Ubuntu which causes this issue.
Thank you for any insights,
Michael
Read More...