Hi, in my case because Raspian have a set of commands (like vcgencmd ) specially for Raspeberry Pi.

Honestly instead of mere workarounds and hacks, I think the solution is for WCG Tech team to:

• Support aarch64 (arm64) on Linux; and
  
• Compile a 64-bit OPN1 AutoDock binary application for this architecture

Once this happens, we'll have much better out-of-the-box support. I'd be more open to building an army of little crunchers then, especially going into the hot summer.

Interesting.....

I've added <alt_platform>arm-unknown-linux-gnueabihf</alt_platform> and now its downloaded a ton of work. thanks.

I'm using the new beta PI 64bit OS so i'll keep an eye on it for errors.

Someone must be missing a trick here. All these power efficient / nano computing boards. I admit not that powerful really, but surely this is where distributed computing becomes powerful.

I had tried
<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
</options>
to get WCG to work on 64-bit Ubuntu Server, and it didn't work after I did...
boinccmd --read_cc_config
boinccmd --project http://www.worldcommunitygrid.org update
But I just learned that I needed to do...
sudo systemctl restart boinc-client
It works!

Edit: Even though it's a 32-bit WCG executable, WCG is running cooler than on 32-bit Raspbian! I am running a Pi 3B running Raspberry Pi OS if that makes any difference.

Regarding Rosetta@home, I see no information to confirm that Rosetta is always (or even usually) 32-bit. As for why a 64-bit Rosetta executable will run without a 64-bit userland (only the kernel is 64-bit), the executable must be stand-alone?

Edit: Oh, I figured it out. Rosetta@home and WCG are statically linked (what the file command returns), not dynamically linked.


I also trust Raspberry Pi OS to not overheat my Pi (via throttling), whereas I'm not so sure about other (64-bit) OSs.

I also like the following command in Raspberry Pi OS...
sudo raspi-config

And running the following command on Ubuntu Server took forever because it installed all kinds of stuff (like Nvidia stuff)
sudo apt-get install boinc

Ubuntu Server also had some fancy security that I didn't care for: updated certain things automatically by default, required me to change password, etc. And I couldn't get Bluetooth to work (if anyone cares).

One thing I liked about Ubuntu Server is that SSH was enabled by default without having to first add a file to the microSD card.

Just found this post from 2017 explaining how to run 32-bit ARM apps on 64-bit ARM devices...
https://boinc.berkeley.edu/forum_thread.php?id=11411
WCG doesn't need the libraries at the top, but I also run Universe@home as a backup, and the C++ library is needed for that.

Hoping for this post to be a complete how-to for using a 64-bit Pi, here is some more info...
In order to edit cc_config.xml,
https://boinc.berkeley.edu/wiki/Client_configuration
I did
sudo nano /var/lib/boinc/cc_config.xml
then I had to run
sudo systemctl restart boinc-client