Pirates@Home logo

Pirates@Home

Berkeley Open Infrastructure
BOINC!
for Network Computing
Home Help Status Forums Glossary Account

Posts by ebahapo

log in
1) Message boards : Wish list : AMD64 (Message 6909)
Posted 4820 days ago by ebahapo

Arrrg! and this is the bit I object to. I know Einstein@Home built this way, and using an old version of Linux seems to the the recommended method, but I really find this distasteful. It should be possible to build backward-compatible apps on a newer release of Linux. You may have to get an older version of GLIBC to link against, but still. Having to build on an old machine is in my mind about as elegant as having to reboot to fix a small problem. You may have to do it from time to time to get work done, but it's not very elegant.

I tried badly to go around this, but even library versioning wouldn't work. And building an older version of GLIBC would not work for dynamic linking, unless it's shipped with the client or linked statically, when the whole thing gets enormous.

This part also worries me. Why is CUPS a dependency? It's not listed in the software prerequisites, so maybe it needs to be listed too? Ideally, you would not need CUPS to build the client software, since CUPS is a printer _server_ system.

Beats me too, but I suspect that it's an indirect dependency.

HTH
2) Message boards : Wish list : AMD64 (Message 6903)
Posted 4821 days ago by ebahapo
Wormholio wrote:
What I would be more interested in are instructions on how to make such a "portable" Linux client. I've tried a few tricks, but not all of it has worked, and I've yet to find clear instructions on how to do this. Not just the steps, mind you, but an explanation of the steps.

Here's a variation of what I posted elsewhere:

  • Assuming access to an older Linux distro with GLIBC 2.3, the most common version, probably under VMware, where to build the client on.
  • Assuming that your compiler of choice is in the search path.
  • Assuming a CURL build with static libraries available with its "curl-config" in the search path.
  • Assuming an OpenSSL build with static libraries available.
  • Assuming a CUPS build with static libraries available.
  • Run the configuration scripts:
    $ _autosetup $ CFLAGS="-O3 -ftree-vectorize" CXXFLAGS="-O3 -ftree-vectorize" FFLAGS="-O3 -ftree-vectorize" ./configure --disable-server --build=x86_64-pc-linux-gnu --enable-client-release --with-ssl=[i]path to OpenSSL build[/i]

  • Run "make".
  • Note the command run to link the client, copy it and paste it into the command-line, making the following changes:

    • Replace "-ldl" with "/usr/lib64/libdl.a".
    • Replace "-lnsl" with "/usr/lib64/libnsl.a".
    • Replace "-lcups" with "path to CUPS build/libcups.a".
    • Replace "-lz" with "/usr/lib64/libz.a".


  • Press enter to relink the client.
  • Voilà!


Perhaps someone familiar with "autoconf" could contribute changes to make this automatic, but I ain't.

HTH

3) Message boards : Wish list : AMD64 (Message 6900)
Posted 4821 days ago by ebahapo
Even though there's an official AMD64 client for Linux, it refers to too many dynamic libraries and requires a fairly recent Linux setup to run on.

So, one more time, I'm making available the AMD64 Linux client here. It refers to a minimal set of standard dynamic libraries whose version requirements should be satisfied by Linux systems up to 2 or 3 years old, however it was built with a fairly recent version of GCC, 4.1.2.

The drill's still the same:


The official AMD64 Windows client can be found here.

For more information, see the BoincStats Forum.

HTH

4) Message boards : Wish list : AMD64 (Message 6416)
Posted 4947 days ago by ebahapo
Here's a development version of the x86-64 Linux client:


The official client for x64 Windows client can be found at boinc_5.10.13_windows_x86_64.exe.

The BOINC client 5.10 can now get 32-bit applications from projects that haven't added support for AMD64 (e.g., Pirates, QMC, etc), provided that they run at least the BOINC server 5.0.9. However, such AMD64 clients for Windows may not get applications from some projects that supported AMD64 before due to a platform name change, at least until such projects are updated.

For more information, see the BoincStats Forum.

HTH

5) Message boards : Pirate Applications : cube 5.13 (Message 6052)
Posted 5001 days ago by ebahapo
Wormholio wrote:
I have also tried your suggestions on chess960 to build against a static version of the library, but ldd says I'm still linking dynamically. So that is another approach which needs more work.

That's probably because you're using g++ to link. Were you sure to link using gcc not g++? That is:

  • For C++:
    gcc ... foo.o -static-libgcc `gcc --print-file-name libstdc++.a`

  • For Fortran:
    gcc ... foo.o -static-libgcc `gcc --print-file-name libgfortran.a` -lgfortranbegin -lm


HTH

6) Message boards : Pirate Applications : cube 5.13 (Message 6035)
Posted 5002 days ago by ebahapo
It's interesting that libstdc++ is sent along but it seems that the project fails to set LD_LIBRARY_PATH before running the application.
7) Message boards : Wish list : AMD64 (Message 5291)
Posted 5076 days ago by ebahapo
Here's the new recommended version for the x86-64 Linux client:


Again, Crunch3r's x64 Windows client can be found at boinc_5.8.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

8) Message boards : Wish list : AMD64 (Message 5012)
Posted 5114 days ago by ebahapo
An updated x86-64 Linux client, version 5.8.15, can be downloaded from boinc_5.8.15_x86_64-pc-linux-gnu.tgz (make sure to read the file "README.x86_64-pc-linux-gnu" in it).

Crunch3r's x64 Windows client, version 5.8.11, can be found at boinc_5.8.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH
9) Message boards : Wish list : AMD64 (Message 4967)
Posted 5121 days ago by ebahapo
Correction: the x86-64 Linux client, version 5.8.11, can be downloaded from boinc_5.8.11_x86_64-pc-linux-gnu.tgz (make sure to copy both files to the BOINC working directory). The new x64 Windows client, version 5.8.11, by Crunch3r, can be found at boinc_5.8.11_windows_amd64.zip.

Update on project applications:

  • Native 64-bit Application Sent to AMD64 Clients

    • SIMAP (Linux)
    • Chess960 (Linux)
    • ABC (Linux)
    • ABC ß (Linux & Windows)
    • Predictor (Linux)
    • RieselSieve (Linux)


  • 32-bit Application Sent to AMD64 Clients

    • SETI & SETI ß (Linux)
    • HashClash (Linux & Windows)
    • Leiden (Linux)
    • Malaria (Linux)
    • Docking (Linux)
    • RieselSieve (Windows)
    • WCG (Linux)
    • Pirates (Linux)


For more information, see BoincStats Forum.

HTH

10) Message boards : Wish list : AMD64 (Message 4934)
Posted 5124 days ago by ebahapo
One test we can try is to run some workunits with the 32 bit version sent to the 64 bit clients and see if the credit claims are reasonable.

So, after 366 WUs, how's it looking like? Aye?


Next 10

Home Help Status Forums Glossary Account


Return to Pirates@Home main page


Copyright © 2021 Capt. Jack Sparrow