Forum > Linux

64-bit science apps based on Rev-2.2B code released

<< < (3/3)

ohiomike:
I've been trying (with little success) to compile an x64 version from the 32b source. Would it be possible to put the x64 source up here so I don't have to track down all the changes needed? I wanted to try the V10.0.023 version of the icc compiler which is supposed to have improved AMD support via the -xO switch. I realize I have a bunch of icc & ipp refs to change, but if I could get the base to work it would help.
 :(  NI!

Simon:
Hi Mike,

http://calbe.dw70.de/2.2b/FINAL_2.2B_LINUX_v2_64bit.tar.bz2 <-- Crunch3r's source snapshot that we compiled the 64-bit Linux apps from.

Compiling is really a b...other.

That said, I recommend you use OpenSuSe 10.2 as a compilation platform, since it'll have all the same lib versions, then adjust the ICC and IPP paths.

First, edit MAKE.ICC to reflect your ICC/IPP directories, then run it.

Second, go inside the client/Optimizer subdirectory and use one of the compile_* scripts (after editing for your system paths) to compile the library with the optimized code.

Then, go up one dir to client/ and copy the corresponding Makefile* (you'll see there are a few with recognizable extensions) to "Makefile" (again, after editing them to reflect your paths). Run "make" inside the client directory.

That's it, provided you'll go with OpenSuSe 10.2 (64-bit, obviously). No guarantees with other distros, we tried and there were quite a lot of problems that weren't really reproducible.

As for running the apps, that's different. Compiling works best there with this source package.

I've been lazy and haven't updated the Linux compilation How-To. Yet another to-do :)

HTH,
Simon.

Crunch3r:

--- Quote from: Simon on 16 Jun 2007, 07:10:30 pm ---Hi Mike,

http://calbe.dw70.de/2.2b/FINAL_2.2B_LINUX_v2_64bit.tar.bz2 <-- Crunch3r's source snapshot that we compiled the 64-bit Linux apps from.

Compiling is really a b...other.

That said, I recommend you use OpenSuSe 10.2 as a compilation platform, since it'll have all the same lib versions, then adjust the ICC and IPP paths.

First, edit MAKE.ICC to reflect your ICC/IPP directories, then run it.

Second, go inside the client/Optimizer subdirectory and use one of the compile_* scripts (after editing for your system paths) to compile the library with the optimized code.

Then, go up one dir to client/ and copy the corresponding Makefile* (you'll see there are a few with recognizable extensions) to "Makefile" (again, after editing them to reflect your paths). Run "make" inside the client directory.

That's it, provided you'll go with OpenSuSe 10.2 (64-bit, obviously). No guarantees with other distros, we tried and there were quite a lot of problems that weren't really reproducible.

As for running the apps, that's different. Compiling works best there with this source package.

I've been lazy and haven't updated the Linux compilation How-To. Yet another to-do :)

HTH,
Simon.

--- End quote ---

Hehe i've allready send him the link about an hour ago via pm on the SETI board :) I was faster  :P



ohiomike:
Thanks Crunch3R/Simon,
I've had good luck the stock Boinc Client and with the optimized 32b app (icc 9.x) under FC6, so I was going to try that first. I'll let you know how it works.

KWSN Holy HndGrena:

--- Quote from: Crunch3r on 13 Apr 2007, 08:37:06 pm ---
--- Quote from: Pam Heinze on 13 Apr 2007, 08:06:29 pm ---Sooo, since I have a pretty big cache, I wonder if anyone has had any experience switching BOINC from 32 to 64 bit in midstream?  Does it cause a problem or should I wait until the cache drains out before switching?

I'll set to no new work, but if I could switch everything now with no ill effects, I'll do it!

Pam

--- End quote ---

Hi Pam,

you'd be on the safe side to let you cache run dry. So that's what i would do.
You might also consider using a 64 bit boinc client (Agustine) provides one.

HTH



--- End quote ---

In my experience (with  xp and 32-bit...) all you need to do is not switch  apps while  running a WU.  Either let your cache run dry, or  (if you have a sufficiently small number of WU's...) suspend all non-running WU's before makeing the switch.  I'm trying (again, with xp pro and 32 bit...) this last approach with a new installation, that's showing 9 hour times for the stock app (I'll get back to ya on how long the WU's actually take - the client is known for lousy initial estimate times...)

Navigation

[0] Message Index

[*] Previous page

Go to full version