Seti@AMD64

Questions and Answers : Unix/Linux : Seti@AMD64

To post messages, you must log in.

AuthorMessage
Per-Arne Hellarvik

Send message
Joined: 3 Apr 99
Posts: 4
Credit: 50,922
RAC: 0
Norway
Message 1296 - Posted: 24 Jun 2004, 19:02:05 UTC

I have a Debian pure 64 install on an AMD64 box...
Boinc compiles cleanly.
But this is the results when I try to run it...
2004-06-24 21:00:33 [SETI@home] Requesting 17280 seconds of work
2004-06-24 21:00:33 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2004-06-24 21:00:33 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-06-24 21:00:33 [SETI@home] Message from server: platform 'x86_64-unknown-linux-gnu' not found
2004-06-24 21:00:33 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-06-24 21:00:33 [SETI@home] No work from project
2004-06-24 21:00:33 [SETI@home] No work from project
2004-06-24 21:00:33 [SETI@home] Deferring communication with project for 1 minutes and 59 seconds
2004-06-24 21:00:33 [SETI@home] Deferring communication with project for 1 minutes and 59 seconds


Anyone got an idea on how to solve this?

ID: 1296 · Report as offensive
morthound

Send message
Joined: 9 Oct 99
Posts: 7
Credit: 361,901
RAC: 0
Sweden
Message 1424 - Posted: 24 Jun 2004, 21:53:37 UTC
Last modified: 24 Jun 2004, 22:00:06 UTC

Have you followed the instructions here: http://boinc.berkeley.edu/anonymous_platform.php

You have to create a app_info.xml file and put it in boinc/projects/setiathome.berkeley.edu/ along with your client.
You have to build the setiathome client too, not just boinc

Hoppas det är till hjälp! :D

ID: 1424 · Report as offensive
Alshain

Send message
Joined: 20 Jul 00
Posts: 1
Credit: 170,270
RAC: 0
United Kingdom
Message 3414 - Posted: 2 Jul 2004, 10:27:33 UTC - in response to Message 1424.

> Have you followed the instructions here:
> http://boinc.berkeley.edu/anonymous_platform.php
>
> You have to create a app_info.xml file and put it in
> boinc/projects/setiathome.berkeley.edu/ along with your client.
> You have to build the setiathome client too, not just boinc

Has anyone had any success compiling the setiathome client on AMD64? If so I'd be interested in a patch.

Alshain

ID: 3414 · Report as offensive
Lord @rchangel

Send message
Joined: 3 Apr 99
Posts: 4
Credit: 606,645
RAC: 0
United States
Message 5707 - Posted: 9 Jul 2004, 17:52:48 UTC - in response to Message 3414.

> > Have you followed the instructions here:
> > http://boinc.berkeley.edu/anonymous_platform.php
> >
> > You have to create a app_info.xml file and put it in
> > boinc/projects/setiathome.berkeley.edu/ along with your client.
> > You have to build the setiathome client too, not just boinc
>
> Has anyone had any success compiling the setiathome client on AMD64? If so I'd
> be interested in a patch.
>
> Alshain
>
I was able to successfully compile the BOINC client, but not the seti_boinc client. When I compile the BOINC client(CVS build 7-9-04) and run it with the appinfo.xml file I get the following output:


2004-07-09 13:51:31 [SETI@home] Requesting 604507 seconds of work
2004-07-09 13:51:31 [SETI@home] Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
2004-07-09 13:51:48 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
2004-07-09 13:51:48 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-07-09 13:51:48 [SETI@home] Started download of 11ja04aa.29978.26386.561076.54
2004-07-09 13:51:48 [SETI@home] Started download of 11ja04aa.29978.26529.617326.127
2004-07-09 13:51:53 [SETI@home] Finished download of 11ja04aa.29978.26386.561076.54
2004-07-09 13:51:53 [SETI@home] Approximate throughput 78529.851686 bytes/sec
2004-07-09 13:51:53 [SETI@home] Started download of 11ja04aa.29978.26529.617326.131
2004-07-09 13:51:53 [SETI@home] execv(../../projects/setiathome.berkeley.edu/boinc_3.19_x86_64-unknown-linux-gnu) failed: -1
2004-07-09 13:51:53 [SETI@home] Starting computation for result 11ja04aa.29978.26386.561076.54_3 using setiathome version 3.19
2004-07-09 13:51:53 [SETI@home] Unrecoverable error for result 11ja04aa.29978.26386.561076.54_3 (process exited with code 2 (0x2))
2004-07-09 13:51:53 [SETI@home] Unrecoverable error for result 11ja04aa.29978.26386.561076.54_3 (process exited with code 2 (0x2))
2004-07-09 13:51:53 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2004-07-09 13:51:53 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2004-07-09 13:51:53 [SETI@home] Computation for result 11ja04aa.29978.26386.561076.54 finished


Then after a while I get the message that was listed in the first post for this thread. Hope this helps to solve whatever problem is going on with the amd64 arch.

ID: 5707 · Report as offensive
David Murray

Send message
Joined: 23 Jul 04
Posts: 3
Credit: 4,679
RAC: 0
New Zealand
Message 19037 - Posted: 29 Aug 2004, 6:40:14 UTC - in response to Message 1424.

> Have you followed the instructions here:
> http://boinc.berkeley.edu/anonymous_platform.php
>
> You have to create a app_info.xml file and put it in
> boinc/projects/setiathome.berkeley.edu/ along with your client.
> You have to build the setiathome client too, not just boinc

The problem is that the setiathome client *won't* compile for 64bit Linux systems.

Certainly I cannot get it to compile under Mandrake 10_64 even tho' the configure script seems to complete as it should. :o(

ID: 19037 · Report as offensive
Merlin
Volunteer tester

Send message
Joined: 24 Nov 99
Posts: 18
Credit: 3,138,613
RAC: 1,352
Germany
Message 19417 - Posted: 29 Aug 2004, 21:25:01 UTC

It is possible to compile boinc and seti_boinc under x86_64. On my Suse-Linux it runs for over one month: see http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=20528

But compiling the client is not easy, some bugs were (are) in the seti_boinc code.

If you post your error_messages, maybe i can help you.

ID: 19417 · Report as offensive
Lord @rchangel

Send message
Joined: 3 Apr 99
Posts: 4
Credit: 606,645
RAC: 0
United States
Message 19458 - Posted: 29 Aug 2004, 22:33:17 UTC - in response to Message 19417.

> It is possible to compile boinc and seti_boinc under x86_64. On my Suse-Linux
> it runs for over one month: see
> http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=20528
>
> But compiling the client is not easy, some bugs were (are) in the seti_boinc
> code.
>
> If you post your error_messages, maybe i can help you.
>
>
>

Ok, so I grabbed the following two source trees:
boinc_public-cvs-2004-08-28.tar.gz
seti_boinc-client-cvs-2004-08-29.tar.gz

moved boinc_public to boinc, it compiles beautifully after running autoconf

extract seti_boinc, do autoconf and configure which finishes neatly. So far every time I run make I get a different error message. First is this:

/usr/src/seti_boinc# make
(cd client; make all)
make[1]: Entering directory `/usr/src/seti_boinc/client'
g++ -g -O2 -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -I.. -I../db -I/usr/src/boinc/api -I/usr/src/boinc/lib -I/usr/src/boinc/image_libs/ -M *.cpp > dependencies
sah_gfx_base.cpp:42:22: boinc_gl.h: No such file or directory
make[1]: *** [dependencies] Error 1
make[1]: Leaving directory `/usr/src/seti_boinc/client'
make: *** [all] Error 2


Next is this:

/usr/src/seti_boinc# make
(cd client; make all)
make[1]: Entering directory `/usr/src/seti_boinc/client'
g++ -g -O2 -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -I/usr/src/boinc/api -I/usr/src/boinc/lib -I/usr/src/boinc/image_libs/ -I.. -I../db -c -o analyzeReport.o analyzeReport.cpp
analyzeReport.cpp: In function `int ReportPulseEvent(float, float, float, int,
int, float, float, float*, int)':
analyzeReport.cpp:337: error: `assert' undeclared (first use this function)
analyzeReport.cpp:337: error: (Each undeclared identifier is reported only once
for each function it appears in.)
make[1]: *** [analyzeReport.o] Error 1
make[1]: Leaving directory `/usr/src/seti_boinc/client'
make: *** [all] Error 2


I could have sworn I was getting three different messages, but anyways, I even saw it hang before on this analyzeReport.cpp. The nearest thing I can figure is that the integers need to be converted into "long"s. Although I've only seen this a problem when they are declared as unsigned integers.

I hope you've got some answers for this, because I'm getting annoyed with putting forth effort towards boinc and not seeing results.

ID: 19458 · Report as offensive
Merlin
Volunteer tester

Send message
Joined: 24 Nov 99
Posts: 18
Credit: 3,138,613
RAC: 1,352
Germany
Message 19479 - Posted: 29 Aug 2004, 23:09:32 UTC

Error "sah_gfx_base.cpp:42:22: boinc_gl.h: No such file or directory": seti_boinc needs boinc-sourcefiles to compile. If your seti_boinc dir is /tmp/seti_boinc, your sourcefiles for boinc should by under /tmp/boinc_public/. Maybe you need a link from /tmp/boinc/ to /tmp/boinc_public/.

If there is no boinc_gl.h under boinc/api/, you need to download this file from cvs (see http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/)
The file boinc_gl.h is here:

http://setiathome2.ssl.berkeley.edu/cgi-bin/cvsweb.cgi/~checkout~/boinc/api/boinc_gl.h?rev=1.2&content-type=text/plain


error: `assert' undeclared (first use this function) is simple - you have to include "assert.h" into analyzeReport.cpp:

add

#include <assert.h>

to this file. There are other includes at top of file.

Maybe you will get this error-message more than ones. Just add this line to all files where the error-mesage appears.


You have also to cast some integers from int to long, for example in file db/xml_util.h on line 384:

change

for (i=0;i<std::min(eol-p,5-npads);i++) {

to

for (i=0;i<std::min(eol-p,(long)5-npads);i++) {


I hope, this helps a little bit :-)

ID: 19479 · Report as offensive
Lord @rchangel

Send message
Joined: 3 Apr 99
Posts: 4
Credit: 606,645
RAC: 0
United States
Message 19770 - Posted: 30 Aug 2004, 3:47:58 UTC - in response to Message 19479.

Awesome stuff Merlin! Wow, I got far with those changes. I had to add that include to one other file, but its skipping my mind which one it is right now.

Unfortunately I've hit a snag and nothing that I've changed seems to help the situation, I'm hoping you can further help me again, you've been invaluable:

/usr/src/seti_boinc# make
(cd client; make all)
make[1]: Entering directory `/usr/src/seti_boinc/client'
g++ main.o analyzeFuncs.o analyzeReport.o analyzePoT.o pulsefind.o gaussfit.o lcgamm.o malloc_a.o seti.o seti_header.o timecvt.o s_util.o version.o worker.o chirpfft.o spike.o progress.o ../db/schema_master_client.o ../db/sqlrow_client.o ../db/sqlblob.o ../db/xml_util.o -L. -looura -lstdc++ -lz -lnsl -lm -ldl -o setiathome-4.3.x86_64-unknown-linux-gnu -L/usr/src/boinc/lib -lboinc
main.o(.text+0xf6): In function `main':
/usr/src/seti_boinc/client/main.cpp:153: undefined reference to `boinc_init'
main.o(.text+0x1a6):/usr/src/seti_boinc/client/main.cpp:174: undefined reference to `boinc_finish'
main.o(.text+0x2a0):/usr/src/seti_boinc/client/main.cpp:181: undefined reference to `boinc_finish'
analyzeFuncs.o(.text+0x842): In function `seti_analyze(ANALYSIS_STATE&)':
/usr/src/seti_boinc/client/analyzeFuncs.cpp:309: undefined reference to `boinc_fraction_done'
analyzeFuncs.o(.text+0x85a):/usr/src/seti_boinc/client/analyzeFuncs.cpp:319: undefined reference to `boinc_fraction_done'
analyzeFuncs.o(.text+0x989):/usr/src/seti_boinc/client/analyzeFuncs.cpp:341: undefined reference to `boinc_fraction_done'
analyzePoT.o(.text+0x21d): In function `analyze_pot(float*, int, int)':
/usr/src/seti_boinc/client/analyzePoT.cpp:332: undefined reference to `boinc_fraction_done'
analyzePoT.o(.text+0x4da):/usr/src/seti_boinc/client/analyzePoT.cpp:234: undefined reference to `boinc_fraction_done'
seti.o(.text+0x3d5f): In function `checkpoint(unsigned char)':
/usr/src/seti_boinc/client/seti.cpp:417: undefined reference to `boinc_time_to_checkpoint'
seti.o(.text+0x425d):/usr/src/seti_boinc/client/seti.cpp:580: undefined reference to `boinc_checkpoint_completed'
worker.o(.text+0x315): In function `read_wu_state':
/usr/src/seti_boinc/client/worker.cpp:120: undefined reference to `boinc_fraction_done'
collect2: ld returned 1 exit status
make[1]: *** [setiathome-4.3.x86_64-unknown-linux-gnu] Error 1
make[1]: Leaving directory `/usr/src/seti_boinc/client'
make: *** [all] Error 2

I also linked boinc to boinc_public, I didn't test it without the link so I'm not certain if it was necessary. I can't believe how stupid it is that they would include boinc_gl.h in the development cvs repository, but not include it into the public cvs repository.

One thing I'd like to point out! I found it necessary to go into the library tree of the boinc client, ie: /usr/src/boinc/lib/ and run 'make' to build the libraries, as seti_boinc needs those in order to compile.

ID: 19770 · Report as offensive
Merlin
Volunteer tester

Send message
Joined: 24 Nov 99
Posts: 18
Credit: 3,138,613
RAC: 1,352
Germany
Message 19896 - Posted: 30 Aug 2004, 20:13:51 UTC

I never had these errormessages. Maybe it helps, if you try an other snapshot of seti_boinc.

ID: 19896 · Report as offensive
Lord @rchangel

Send message
Joined: 3 Apr 99
Posts: 4
Credit: 606,645
RAC: 0
United States
Message 20129 - Posted: 31 Aug 2004, 1:38:13 UTC - in response to Message 19896.

IT FINALLY COMPILED!!!!!!!!!

The last error message I got was due to it not liking the libraries that are used in the boinc_public directory(They havn't been changed in over 2 months).

I grabbed a CVS version of boinc, date 8-30-04, did the exact same things listed in the posts previous to this one and it compiled cleanly.

Also: link from boinc_public to boinc didn't matter.


Um....one problem.....when I execute the compiled file in /seti_boinc/client/ it does nothing. I can do ./setiathome* -version and it gives me information, but I can't really DO anything with the client.

Next I created the app_info file and added the setiathome version information, but I still got errors. I later learned that what you do is the following:

Copy the client out of /boinc/client/ to whatever location you're running boinc. Secondly add the setiathome client found in /seti_boinc/client/ to the same directory that you created the app_info.xml

my app_info.xml file looks as follows:



setiathome


setiathome-4.3.x86_64-unknown-linux-gnu


setiathome
403

setiathome-4.3.x86_64-unknown-linux-gnu






(version_num can be retrieved through doing "setiathome-4.3.x86_64-unknown-linux-gnu -version)

ID: 20129 · Report as offensive

Questions and Answers : Unix/Linux : Seti@AMD64


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.