Open DougieLawson opened 3 years ago
The solution is to install libnewlib-arm-none-eabi and libstdc++-arm-none-eabi-newlib.
This actually got picked up before launch. The manual install instructions have been changed in the Getting Started guide. However the only circumstances we have seen this is where apt
is being forced to not install requirements. This shouldn't happen when running pico-setup.sh
as it has control over how apt
is being called. Do you have any unusual global configuration setup that might cause it to not install additional requirements?
And FYI I did test a pure 32-bit install and a pure 64-bit install before launch, and they both worked fine (after some tweaks #4 ), I just didn't test a mixed 64/32-bit installation.
Do you have any unusual global configuration setup that might cause it to not install additional requirements?
This is stock standard Raspbian Buster frequently upgraded with the 5.10.10 kernel installed with rpi-update. It's nothing special apart from 32-bit userland and the 64-bit kernel. The exact same software build (but without the 64-bit kernel) runs on my RPi2B (and seven other Raspberries).
If I've reached the point of running the script then I'm beyond the point of reading that stuff in the docs, so saying stuff is "documented" is a fatuous answer. Just change the script - because otherwise the naïve user will come a cropper on this.
Running pico_setup.sh on a RaspiOS system built as 32-bit userland but running with the 64-bit 5.10.10 kernel fails with
The solution is to install libnewlib-arm-none-eabi and libstdc++-arm-none-eabi-newlib.
pico-setup.sh needs to be updated to include those two pieces.