ABC@Home has a real 64-bit application, which runs 3 times faster than the 32-bit one due to the nature of their calculations. Other projects don't have 64-bit apps. Why do you assume that if one did it the rest would as well?

ABC@Home has a real 64-bit application, which runs 3 times faster than the 32-bit one due to the nature of their calculations. Other projects don't have 64-bit apps. Why do you assume that if one did it the rest would as well?

Chess and SIMAP are supposed to be 64-bit apps too.

---

Pirates is testing Hello 5.11 at the moment, sending 32bit applications to 64bit clients.

---

ABC@Home has a real 64-bit application, which runs 3 times faster than the 32-bit one due to the nature of their calculations. Other projects don't have 64-bit apps. Why do you assume that if one did it the rest would as well?

You're funny, Nick. Why do you assume that when I detail one scenario, I have assumed the opposite scenario?

:)

Well according to this Seti does have a Linux 64 bit app but the problem is Seti doesn't used the official boinc platform name of "x86_64-pc-linux-gnu" but instead uses "x86_64-unknown-linux-gnu" or something similar for 64 bit Linux apps so the only solution is choose seti only for 64 bit or other projects and not seti as im fairly certain other projects are using the official BOINC platform name and i don't think the Client can report under two names.

Hopefully Seti decides to follow the official platform name guidelines soon.

When I select run_client, the client runs, when I select run_manager, nothing happens.

Only the core client is replaced with a 64-bit one. The original 32-bit manager can still be run without problems alongside the 64-bit client (see README.x86_64-pc-linux-gnu from my tar ball).

Try "boincmgr" instead.

HTH

Installed your "new" 5.8.17 with same results. I can run client just fine and cannot run manager.

How much trouble is it to compile the manager too?

Thank you.