Hi @kentisevil, I may make a 64 bit release in the future but right now I don't have a 64 bit OS installed and I think I will wait a little for it to mature before I try.
Is it worth copying all the files in the /usr/lib/arm-linux-gnueabihf directory on a 32 bit installation to the 64 bit machine and adding that to the LD_LIBRARY_PATH? Maybe also need some from /lib/arm-linux-gnueabihf as well?
Edited by burtoogle
Recommended Posts
Top Posters In This Topic
45
9
8
6
Popular Days
May 12
8
Jul 23
8
Aug 2
8
Mar 4
6
Top Posters In This Topic
burtoogle 45 posts
icare 9 posts
stevepos 8 posts
ahoeben 6 posts
Popular Days
May 12 2020
8 posts
Jul 23 2020
8 posts
Aug 2 2019
8 posts
Mar 4 2020
6 posts
Popular Posts
burtoogle
Now available is a Linux AppImage that runs on an armhf system (e.g. a Pi 4). It has received minimal testing but it does appear to work (I sliced a benchy OK!). Obviously, even the amazin
burtoogle
This is my first post for years. I really don't post here any more but I just have to reply to the last post because it's just so wrong on many counts. @Varkanoid, do yourself a favour and completely
burtoogle
I have managed to workaround the various limitations and bugs in the graphic library and now have quite a nice display. It still has some compromises compared to the other builds (Linux/Mac/Windows) a
Posted Images
kentisevil 0
Hi Burt - would you consider compiling one for the new 64bit Beta RaspberryPi OS? https://www.raspberrypi.org/forums/viewtopic.php?t=275370 I tried running the latest version (installed the mesa tarball and libgles-dev) however it balks and barks about libz.so - which is on my system - however when I put it in my LD_LIBRARY_PATH it says:
<code>
./Cura-mb-master-armhf-20200610.AppImage
./Cura-mb-master-armhf-20200610.AppImage: error while loading shared libraries: libz.so: wrong ELF class: ELFCLASS64
</code>
Link to post
Share on other sites