Hello, I was trying to compiling the seti enhanced client because there isn't an optimized client for Athlon-XP CPU's. The better I found is a generic SSE optimized one.

So I tried to retrieve the sources but I don't understand what I have to download.

I followed the S@H website pages and I reached the nightly tarball page, but they are "nightly" and I don't know which of them are for use in the main and what in the beta project.

Next, I tried to download the package provided by lunatics.at but it requires an Intel proprietary compiler. The site links also at http://setiathome.berkeley.edu/~korpela/build/i686-linux/ but the tarballs are no longer supplied there.

Next, I tried to retrieve the sources with cvs, software I had never used before, and I gave this command to the shell: cvs -d :pserver:anonymous@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout -r seti_enhanced seti_boinc
Then it downloaded some stuff, but may files are missing: maybe the tag I used was the wrong one?

So, what's the best and simplest way to retrieve the seti client sources for use in the main project?

Thank you, Massimiliano

---

CVS or the nightly tarballs are the easiest way to download. Also you need to download and compile the boinc client and libfftw, too.
But, at the BOINC third party site (boinc.berkeley.edu/download_other.php) are still a lot of binaries for Linux which was optimized for SSE available.

---

CVS or the nightly tarballs are the easiest way to download. Also you need to download and compile the boinc client and libfftw, too.
But, at the BOINC third party site (boinc.berkeley.edu/download_other.php) are still a lot of binaries for Linux which was optimized for SSE available.

I have already compiled the boinc client and libfftw and I have alreadly checked the third party sites: I found only a generic SSE optimized one (lunatics.at) which was compiled with an Intel compiler. I want to compile with Athlon-XP architecture optimization.

I wasn't able to download the client with CVS: which tag should I use? The checkout of seti_boinc with -r seti_enhanced didn't downloaded all the necessary files. The other tags are not "enhanced" or are beta.

About tarballs: how can I know which of them are for use in the beta project and which are instead for use in the main project?

---

CVS or the nightly tarballs are the easiest way to download. Also you need to download and compile the boinc client and libfftw, too.
But, at the BOINC third party site (boinc.berkeley.edu/download_other.php) are still a lot of binaries for Linux which was optimized for SSE available.

I have already compiled the boinc client and libfftw and I have alreadly checked the third party sites: I found only a generic SSE optimized one (lunatics.at) which was compiled with an Intel compiler. I want to compile with Athlon-XP architecture optimization.

The Lunatics has a modified (optimized) source. The Intel compiler is a lot of faster than gcc.
Stefan Urbat has also a Linux AMD64 binary, which was made from the offical source and compiled with gcc and optimized for AMD64.

I wasn't able to download the client with CVS: which tag should I use? The checkout of seti_boinc with -r seti_enhanced didn't downloaded all the necessary files. The other tags are not "enhanced" or are beta.

This should be the right command. But what is happens at a checkout without the -r seti_enhanced ?

About tarballs: how can I know which of them are for use in the beta project and which are instead for use in the main project?

So far I know is there no way to see this. But June/July 2006 would be a 5.15.

---

Intel compiler is proprietary sw and I'd like to use free software when I can, furthermore I use an AMD cpu, so I don't know how much the Intel compiler generic SSE optimization would be faster on a AMD than a specific arch optimization made with gcc.

The cvs checkout didn't retrieved, in example, the _autosetup script. I downloaded it separately but one of configuration scripts, I don't remember which, claimed that some file were still missing.

Now I think the best thing to do is to download one of the nightly tarballs and then see what version is it.

I take advantage to inform that something seems to be wrong in the _autosetup scripts I have launched from various sources: they don't tests correctly the pkg-config version, and it fails even if the version is correct.
When it retrieves the pkg-config version, pkg-config returns only the number, not other informations like software name and license that are generally removed by this instruction in order to obtain a numeric value:
version=`echo $version | awk '{ for (i=1;i<=NF;i++) { split($i,j,"."); m=j[1]"."j[2] ; if ((m*1)>0) { print m ; break; } } }'`
Before that instruction the $version retrieved from pkg-config --version is, i.e. 0.21, after that it's a void string, so the test fails (at least on my system). I solved the problem editing the script and bypassing the pkg-config version check. I don't know wether it's a problem of my computer or there's a bug to fix, I report it here nevertheless.

Thank you for the advices. Greetings.

---