if I have to start debugging installation script errors on the outstart... I usually move on to a better platform before lunch time comes up.
Besides the fact it did not manage to complete the compilation and linking process, it did so very slowly (I am using a Raspberry 3)...showing the platform isn't adequate.
Hint: if you want to use a Raspberry Pi, use a a Raspberry 4.
After completing the OS installation as instructed, I stumped on a link error within a minute or so from launching the setup.sh
Never a good sign when a release doesn't link. Obviously something happened during the OS installation ... namely, it updated. The instructions never say not to let the OS update after installation.. I think that's where the problems come from.
I am not verifying this... but it's quite obvious the developers released the package on a different system configuration.
Never the less, I found a fix... or so it appeared, which suggested to change the version of a library ... RED FLAG!!
If you need to go in and start messing with the building script, you are setting yourself up for a lot of pain.
And so it was ...after more than a hour or so of painfully slow compilation riddled with language warnings... never a good sign,... it finally threw a depressive "...atomic_base.h:396: undefined reference..." error.
This is a classic type of error that takes place only when the wrong library is being used.
IF YOUR GIRLFRIEND NEEDS HIGH MAINTENANCE, CHANGE GF.
Alexa, our love story is in serious troubles.
So, I am dumping the Raspberry...I am moving onto a full Ubuntu capable platform (NVIDIA Jetson nano).
If you encountered similar issues with the Raspberry ... delete everything and try again making sure the OS does not update after installation. No guarantees it will work.
In any case ... I'd suggest to use a Raspberry 4.
So far I am not impressed...