MD64 3500+, kernel 2.6.9-r14

I compiled version 4.11 succesfully on my amd64.
I ungziped the gz-file
I did ./configure, cd client, make and make install.

So far so good. Then I copied the files to /home/boinc

Then I succesfullie contacted the server. The problem is that the server states that it states:

Code:
cat sched_reply_www.climateprediction.net.xml
--snap--
platform 'x86_64-unknown-linux-gnu' not found
--snap--


Then it says:
Code:

2005-01-25 13:38:32 [---] Starting BOINC client version 4.11 for x86_64-unknown-linux-gnu
2005-01-25 13:38:32 [http://www.climateprediction.net/] Project prefs: no separate prefs for home; using your defaults
2005-01-25 13:38:32 [climateprediction.net] Host ID is 89067
2005-01-25 13:38:32 [---] No general preferences found - using BOINC defaults
2005-01-25 13:38:32 [climateprediction.net] Deferring communication with project for 23 hours, 24 minutes, and 2 seconds
2005-01-25 13:38:32 [climateprediction.net] Deferring communication with project for 23 hours, 24 minutes, and 2 seconds


Does anyone know how to solve this? It seems like the server doesn't know what kind of package it must send, but that is just a gues .

Greetings Elmar

---

Sorry, but there is NO 64 bit version of CP.
Compiling BOINC for 64 bits is of no use.
The <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/tech_faq_boinc.php"> tech_faq</a> page shows what is available.

It's a matter of money; 64 bit cpus showed up long after conversion of the code from the super computer
fortran to desktop pcs had started. The project team would need to buy a new compiler, (with license),
a suitable editor, (with license), a 64 bit computer on which to work, and money to pay the programmer(s).
The currently employed programmers are hard at work on the new programs.

But you are not alone in wishing for a 64 bit version.

Les

OK, so be it, but how do I trick my 64 bit boinc into downloading 32 bit workunits? I do have 32 bit emulation (or native support, or whatever) Is there a way to write up the app_info.xml file to do this, or are we stuck running just seti?

&gt; Sorry, but there is NO 64 bit version of CP.
&gt; Compiling BOINC for 64 bits is of no use.
&gt; The <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/tech_faq_boinc.php">
&gt; tech_faq</a> page shows what is available.
&gt;
&gt; It's a matter of money; 64 bit cpus showed up long after conversion of the
&gt; code from the super computer
&gt; fortran to desktop pcs had started. The project team would need to buy a new
&gt; compiler, (with license),
&gt; a suitable editor, (with license), a 64 bit computer on which to work, and
&gt; money to pay the programmer(s).
&gt; The currently employed programmers are hard at work on the new programs.
&gt;
&gt; But you are not alone in wishing for a 64 bit version.
&gt;
&gt; Les
&gt;
&gt;

---

I'm out of my depth with this, but similar questions have been asked before.
I did a seach for 'compile', and <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=1500"> this</a> is one that I found.
If it doesn't help, you could try a search, perhaps on 'compiled' or 'compiling'.
And some of the Linux people should show up when it's 'their daytime'.

Les

&gt; OK, so be it, but how do I trick my 64 bit boinc into downloading 32 bit
&gt; workunits? I do have 32 bit emulation (or native support, or whatever) Is
&gt; there a way to write up the app_info.xml file to do this, or are we stuck
&gt; running just seti?
&gt;

I guess the question I have is what advantage 64 bit BOINC gives you over 32 bit BOINC. It's the client, if compiled in 64 bit, that would result in a performance increase (decrease in WU duration). And, of course, the CPDN client is not open source.

But I don't really know about what this would do in other BOINC projects. Perhaps I misunderstand...

&gt; Sorry, but there is NO 64 bit version of CP.
&gt; Compiling BOINC for 64 bits is of no use.
&gt; The <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/tech_faq_boinc.php">
&gt; tech_faq</a> page shows what is available.
&gt;
&gt; It's a matter of money; 64 bit cpus showed up long after conversion of the
&gt; code from the super computer
&gt; fortran to desktop pcs had started. The project team would need to buy a new
&gt; compiler, (with license),
&gt; a suitable editor, (with license), a 64 bit computer on which to work, and
&gt; money to pay the programmer(s).
&gt; The currently employed programmers are hard at work on the new programs.
&gt;
&gt; But you are not alone in wishing for a 64 bit version.
&gt;
&gt; Les
&gt;
&gt;
Those are all very poor excuses. I'm going to run Seti@home on my 64 bit computer instead.

Why not run under 32bit mode for a while?
Since my original post the project people have acquired the necessary 64bit items and are working on a 64bit version of the sulphur model, currently in alpha testing.

And "Linux 2.6.12-we-used-to-be-friends" is NOT an acceptable os name.