Could you tell us what linux distribution you use to compile the seti app?

Centos-4.3, Fedora Core-3, and Fedora Core-4. (All Red Hat derivatives to the dismay of many)

Perhaps it would help if you posted a tarball of your complete seti folder, containing a working set of configuration files.
(I don't know if this is possible, though...)

I've linked my entire build tree (except for windows since it's on a different machine) into my web directory, that way you can see how it is at any time....
I've also tarred up all the linux directories.

Be warned that these are my active development direcories so I can't guarantee what's there will compile at any given instant.

http://setiathome.berkeley.edu/~korpela/build/

Eric

Eric

---

@SETIEric@qoto.org (Mastodon)

Thanks a lot!

Regards Hans

---

Gecko

That is one of the most intelligent this I have see posted!

Crunch3r had paid for the software out of his pocket... and it was the latest.. including as he renewed the license for IPP... That was part of the delay for the optimized 5.12... It produced even tighter code...

Opps water under the bridge...

I would suggest that if it would/could somehow be donated to Eric, then some of the issues with Seti Enhanced might be solved...

Pappa

Before anyone spends money, the eval. compiler and IPP can be downloaded. To get "legal" we can then scrape together the bucks and buy something.

At the same time, if Eric has any interest in doing this, he can get the Academic license ($100/compiler, $50/IPP) and as far as I can tell, there are no limits for distribution.

I was just thinking, there is another whole approach here:

The "eval" compiler and IPP library is available from Intel, for *nix and Windows.

Someone could put together a kit, and a set of instructions.

Download and install the compiler, download and install IPP, download the SETI sources, and go.

The binaries wouldn't be distributable, but who cares.

---

This might be due to what software/libraries you are using on your linux machine. If you use _autosetup to build the configure script on your Mac, you can probably copy the configure file over to your linux system. That may solve the problem. If you are using a prebuilt configure script, you might just try running _autosetup on you linux machine.

Eric

I just can't get any of the nightly builds to compile on linux, even the same one that compiles just fine on my Mac.

I'm doing:

./configure --disable-server --disable-server

I also tried:

./configure --disable-server --disable-server --enable-static

then:

make

I end up with an error of:

if g++ --include ../config.h -DDYNAMIC_GRAPHICS=1 -DHAVE_CONFIG_H -I. -I. -I.. -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -I../db -I/home/boog/build_boinc/boinc/api -I/home/boog/build_boinc/boinc/lib -pthread -O2 -Wall -MT seti_boinc-main.o -MD -MP -MF ".deps/seti_boinc-main.Tpo" -c -o seti_boinc-main.o ; then mv -f ".deps/seti_boinc-main.Tpo" ".deps/seti_boinc-main.Po"; else rm -f ".deps/seti_boinc-main.Tpo"; exit 1; fi
g++: no input files
make[2]: *** [seti_boinc-main.o] Error 1

if I do make -k:

make[2]: *** [fakedata-xml_util.o] Error 1
make[2]: Target `all' not remade because of errors.
with alot of scrolling "red" text


btw, I have all the libraries installed, and boinc built just fine, even did a "make install" of boinc just to make sure all the libraries were in the right place.

I'm stumped!

Hi Eric, thanks for the reply!

I tried to run _autosetup then re ran configure with the same options, and make gives the same errors.

I built the mac client using the xcode gui, so it doesn't use the scripts from the command line.

should I be using nightly builds? or should I checkout the cvs stable branch? It seems I don't get all the files if I use the directions for getting the cvs from the "make your own" links.

@Sir Ulli
Thanks, I have used the directions from his site to try to build (actually it's what got me started), all the directions for building boinc work from there, it's just seti that I am having problems with.





BTW I am using suse 10.0.

---

Could you tell us what linux distribution you use to compile the seti app?

Centos-4.3, Fedora Core-3, and Fedora Core-4. (All Red Hat derivatives to the dismay of many)

Perhaps it would help if you posted a tarball of your complete seti folder, containing a working set of configuration files.
(I don't know if this is possible, though...)

I've linked my entire build tree (except for windows since it's on a different machine) into my web directory, that way you can see how it is at any time....
I've also tarred up all the linux directories.

Be warned that these are my active development direcories so I can't guarantee what's there will compile at any given instant.

http://setiathome.berkeley.edu/~korpela/build/

Eric

Eric

Awesome! thanks!

I'm downloading now!

---

I've linked my entire build tree (except for windows since it's on a different machine) into my web directory, that way you can see how it is at any time....
I've also tarred up all the linux directories.

Be warned that these are my active development direcories so I can't guarantee what's there will compile at any given instant.

http://setiathome.berkeley.edu/~korpela/build/

Eric

Eric

hmmmm....still getting errors with the tarball from your site, the g++ no input files is gone, but it was replaced with :

make[2]: *** [seti_boinc-main.o] Error 1
make[2]: Leaving directory `/home/boog/build_boinc/seti_boinc/client'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/boog/build_boinc/seti_boinc'
make: *** [all] Error 2

the other one is still the same:

make[2]: *** [fakedata-xml_util.o] Error 1
make[2]: Target `all' not remade because of errors.
make[2]: Leaving directory `/home/boog/build_boinc/seti_boinc/tools'
make[2]: Entering directory `/home/boog/build_boinc/seti_boinc'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/boog/build_boinc/seti_boinc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/boog/build_boinc/seti_boinc'
make: *** [all] Error 2

---

Hi boog,

I fixed some bugs I found so far, but still can't get seti_boinc compiled.

What I have found until now:

in client/s_util.h there's some extra text that needs to be commented out:

Change this

// macro so we can get file and line info.
<<<<<<< s_util.h
#define SETIERROR( err, errmsg ) do { \\
        FORCE_FRAME_POINTER; \\
	throw seti_error( err, __FILE__, __LINE__, errmsg  ) \\
} while (0)
=======
#define SETIERROR( err, errmsg ) do { \\
        FORCE_FRAME_POINTER; \\
	throw seti_error( err, __FILE__, __LINE__, errmsg  ); \\
} while (0)
>>>>>>> 1.12.2.6

to this

// macro so we can get file and line info.
/*
<<<<<<< s_util.h
#define SETIERROR( err, errmsg ) do { \\
        FORCE_FRAME_POINTER; \\
	throw seti_error( err, __FILE__, __LINE__, errmsg  ) \\
} while (0)
=======
*/
#define SETIERROR( err, errmsg ) do { \\
        FORCE_FRAME_POINTER; \\
	throw seti_error( err, __FILE__, __LINE__, errmsg  ); \\
} while (0)
/*
>>>>>>> 1.12.2.6
*/

There are some references to a not (yet) existing "boinc_worker_timer"
I added the following to the beginning of "config.h.in" to get rid of these

#define boinc_worker_timer(x)

You need to run "./configure" after this.

I'm currently trying a compile with gcc-3.4, since gcc-4.0 (my default) didn't work.

Regards Hans

---

...
There are some references to a not (yet) existing "boinc_worker_timer"
...
Regards Hans

That function is in the BOINC source api/boinc_api.C file. Eric added it and some other related things, Rom Walton has also made some recent changes. You'll probably need to get the latest BOINC sources to build successfully.

                                              Joe

Hi boog,

I fixed some bugs I found so far, but still can't get seti_boinc compiled.
---snip---

You need to run "./configure" after this.

I'm currently trying a compile with gcc-3.4, since gcc-4.0 (my default) didn't work.

Regards Hans

Hey, Hans,

Thanks for the info!

I don't know why I didn't think of that before! In my quest of building the mac clients I found that gcc-4 would not work.

Now to see if IT will build, or go thru dependency hell with rpm's.

---

...
There are some references to a not (yet) existing "boinc_worker_timer"
...
Regards Hans

That function is in the BOINC source api/boinc_api.C file. Eric added it and some other related things, Rom Walton has also made some recent changes. You'll probably need to get the latest BOINC sources to build successfully.

                                              Joe

Thanks.

My progress (or lack thereof) so far:

g++-4.0 or g++-4.1 can't compile the source, probably because of stricter interpretation of the C++ syntax.

g++3.3 or g++3.4 fail at the final link stage. I guess my binutils have the wrong version:

"GNU ld version 2.16.91 20060413 Debian GNU/Linux"


Regards Hans

P.S: I'm trying icc now....

---

...
There are some references to a not (yet) existing "boinc_worker_timer"
...
Regards Hans

That function is in the BOINC source api/boinc_api.C file. Eric added it and some other related things, Rom Walton has also made some recent changes. You'll probably need to get the latest BOINC sources to build successfully.

                                              Joe

Thanks.

My progress (or lack thereof) so far:

g++-4.0 or g++-4.1 can't compile the source, probably because of stricter interpretation of the C++ syntax.

g++3.3 or g++3.4 fail at the final link stage. I guess my binutils have the wrong version:

"GNU ld version 2.16.91 20060413 Debian GNU/Linux"


Regards Hans

P.S: I'm trying icc now....

I installed gcc-3.4 and I got the same exact errors as before (using the source from eric's site), and they are the same errors with icc.

I'm giving up for tonight, time for bed.

---

...
There are some references to a not (yet) existing "boinc_worker_timer"
...
Regards Hans

That function is in the BOINC source api/boinc_api.C file. Eric added it and some other related things, Rom Walton has also made some recent changes. You'll probably need to get the latest BOINC sources to build successfully.

                                              Joe

Thanks.

My progress (or lack thereof) so far:

g++-4.0 or g++-4.1 can't compile the source, probably because of stricter interpretation of the C++ syntax.

g++3.3 or g++3.4 fail at the final link stage. I guess my binutils have the wrong version:

"GNU ld version 2.16.91 20060413 Debian GNU/Linux"


Regards Hans

P.S: I'm trying icc now....

I installed gcc-3.4 and I got the same exact errors as before (using the source from eric's site), and they are the same errors with icc.

I'm giving up for tonight, time for bed.

I'm just downloading a Centos ISO :o)

Regards Hans

P.S: I'm giving up for now as well...

---

Picking up from Sir Ulli, anyone know the whereabouts of Ned and Harold?
Are they still active in the Seti community?

Hi Gecko,

I'm still actively participating in the project, but won't be participating in optimizing/compiling seti_enhanced applications.

TBH, I no longer have the inclination to make the huge time investment required given the somewhat fickle nature of _some_ elements of this community :(

I did my bit way back when, and got the ball rolling... it's time for some others to step up to the plate now if the community wants optimized seti builds. The tools and source are all freely available (at least for linux), so it shouldn't be too hard for anyone who has the time and inclination :)

I'll leave my site up as an historical reference, but won't be updating it with enhanced clients.

I always had good success building on RedHat-based derivatives (see Eric's statement above), and can thoroughly recommend CentOS 4 as a great distro (although it does still use gcc 3.4, which is great for general compatability, but _may_ not produce optimal results in terms of optimizing the seti application).

Regards,

Ned

---

*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***

I can help some for Linux (and for FreeBSD, the same applies.) here. You need gcc-3.3 or 3.4 (or maybe 3.2). 4.x doesn't work for me.

As for ICC & IPP, I usually use this way (sse2 for example, from my memo, I copy & paste these commands. This is a good point in unix-like OS's):

in boinc directory (after ./_autosetup):

1. ./configure --disable-server --enable-maintainer-mode --disable-client

2. make clean

3. make AR=xiar CC=icc CXX=icpc CFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" CXXFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" MYSQL_CONFIG=true

(if you are using icc 9.0, you should use "-fp-model fast")

in seti_boinc directory,
1. ./configure --disable-server --enable-sse2 --with-ipp=/opt/intel/ipp/5.1/ia32 --enable-maintainer-mode --disable-graphics

2. make clean

3. make AR=xiar CC=icc CXX=icpc CFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" CXXFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" LDFLAGS="-L/opt/intel/ipp/5.1/ia32/lib -lsvml -i-static" MYSQL_CONFIG=true

The environment variables "USE_IPP" or "USE_SSE2" or ipp libraries doesn't have to be given explicitly. "./configure --with-ipp=.... --enable-sse2" will give these macros in config.h, Makefile automatically (thanks Eric!!)

Now I'm actively using ICC for linux for other apps like scilab.

---

Luckiest in the world. WMD = Weapon of Mass Distraction.
Click this table.

I'm just downloading a Centos ISO :o)

Regards Hans

P.S: I'm giving up for now as well...

I am going to install Fedora Core 4, I have had it on this box before, I just prefer using suse, but for a now dev/http box fedora should be just fine since I relenquished it's other duties (except for crunching).

---

I can help some for Linux (and for FreeBSD, the same applies.) here. You need gcc-3.3 or 3.4 (or maybe 3.2). 4.x doesn't work for me.

As for ICC & IPP, I usually use this way (sse2 for example, from my memo, I copy & paste these commands. This is a good point in unix-like OS's):

in boinc directory (after ./_autosetup):

1. ./configure --disable-server --enable-maintainer-mode --disable-client

2. make clean

3. make AR=xiar CC=icc CXX=icpc CFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" CXXFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" MYSQL_CONFIG=true

(if you are using icc 9.0, you should use "-fp-model fast")

in seti_boinc directory,
1. ./configure --disable-server --enable-sse2 --with-ipp=/opt/intel/ipp/5.1/ia32 --enable-maintainer-mode --disable-graphics

2. make clean

3. make AR=xiar CC=icc CXX=icpc CFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" CXXFLAGS="-sox -xW -O3 -fp-model fast=2 -no-prec-div -no-prec-sqrt -ipo" LDFLAGS="-L/opt/intel/ipp/5.1/ia32/lib -lsvml -i-static" MYSQL_CONFIG=true

The environment variables "USE_IPP" or "USE_SSE2" or ipp libraries doesn't have to be given explicitly. "./configure --with-ipp=.... --enable-sse2" will give these macros in config.h, Makefile automatically (thanks Eric!!)

Now I'm actively using ICC for linux for other apps like scilab.

AWESOME!

Thank you!

I saved this info in a text file.

now off to rebuild my box as fedora......

---

Thanks for your help Tetsuji!

I've got all necessary stuff (sources from Eric's links, Intel compiler + IPP + licenses), but I just can't get seti_boinc to configure. It keeps giving me this error (haven't seen that one before):

checking size of long int... configure: error: cannot compute sizeof (long int), 77
See `config.log' for more details.

config.log

configure:42105: checking size of long int
configure:42424: g++ -o conftest  -I/usr/include -I/usr/include/openssl -I/opt/intel/ipp/5.1/ia32/include -I/opt/intel/ipp/5.1/ia32/
tools/staticlib   -L/usr/lib -nodefaultlibs -L/opt/intel/ipp/5.1/ia32/lib conftest.cc  -lssl -lcrypto /usr/lib/libcrypto.a /usr/lib/
libssl.a -Wl,-Bdynamic -ldl -Wl,-Bdynamic -lm /usr/lib/libnsl.a -Wl,-Bdynamic -lrt /usr/lib/libz.a -Wl,-Bdynamic -lgcc_eh -Wl,-Bdyna
mic -lpthread -Wl,-Bdynamic -lc -lippcore -lippsmerged >&5
/tmp/cc6OoaL7.o:(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status
configure:42427: $? = 1     
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "setiathome_enhanced"
| #define PACKAGE_TARNAME "setiathome_enhanced"
| #define PACKAGE_VERSION "5.12"
| #define PACKAGE_STRING "setiathome_enhanced 5.12"

...and so on.

Anyone have an idea how to get it to go over that configure check? I'm pretty sure my libs are up to date. Will do an apt-get update/upgrade and try again then, but I'm not very hopeful about that.

Other than that, it compiled the BOINC client using the intel compiler fine.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Thanks for your help Tetsuji!

I've got all necessary stuff (sources from Eric's links, Intel compiler + IPP + licenses), but I just can't get seti_boinc to configure. It keeps giving me this error (haven't seen that one before):

checking size of long int... configure: error: cannot compute sizeof (long int), 77
See `config.log' for more details.

config.log

configure:42105: checking size of long int
configure:42424: g++ -o conftest  -I/usr/include -I/usr/include/openssl -I/opt/intel/ipp/5.1/ia32/include -I/opt/intel/ipp/5.1/ia32/
tools/staticlib   -L/usr/lib -nodefaultlibs -L/opt/intel/ipp/5.1/ia32/lib conftest.cc  -lssl -lcrypto /usr/lib/libcrypto.a /usr/lib/
libssl.a -Wl,-Bdynamic -ldl -Wl,-Bdynamic -lm /usr/lib/libnsl.a -Wl,-Bdynamic -lrt /usr/lib/libz.a -Wl,-Bdynamic -lgcc_eh -Wl,-Bdyna
mic -lpthread -Wl,-Bdynamic -lc -lippcore -lippsmerged >&5
/tmp/cc6OoaL7.o:(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status
configure:42427: $? = 1     
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "setiathome_enhanced"
| #define PACKAGE_TARNAME "setiathome_enhanced"
| #define PACKAGE_VERSION "5.12"
| #define PACKAGE_STRING "setiathome_enhanced 5.12"

...and so on.

Anyone have an idea how to get it to go over that configure check? I'm pretty sure my libs are up to date. Will do an apt-get update/upgrade and try again then, but I'm not very hopeful about that.

Other than that, it compiled the BOINC client using the intel compiler fine.

I think I got a similar error to this when I was chaning/playing with environment stuff like:

export CC=gcc;export CXX=g++

I just can't remember exactly what it was that I messed with that gave me that error, other things I messed with would tell me that the compiler couldn't build executeables.

Sorry, that's about the best that I can help with.

---

I think I got a similar error to this when I was chaning/playing with environment stuff like:

export CC=gcc;export CXX=g++

I just can't remember exactly what it was that I messed with that gave me that error, other things I messed with would tell me that the compiler couldn't build executeables.

Sorry, that's about the best that I can help with.

Thanks, I'll try that. Wonder how that'll work since I'm trying to build it with the Intel compiler though :)

In any case, apt-get upgrade is still running, I'll see if anything changes after that.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Which is why I went to Intel's web site, and read what I could find on the subject.

If you buy a copy using "student pricing" then there is a clause that says "non-commercial use only" which I think means you can't sell programs.

That would do it for us anyway, wouldn't it ?
It's not like anyone would take money for releasing a Optimized version.

Crystallize,
First, I will be the first to admit that I'm not a lawyer, and I don't know about the rights etc. for any software licenses for a *specific* piece of software. I was just questioning the legality of using a certain piece of software for a certain purpose. I have been around computers and software ever since before the IBM PC was released and I have seen all sorts of "licensing agreements". You seemed to be saying that your student license agreement for one piece of software could apply to *all* student software. In my experience I have found this not to be true. Especially when you consider the totally different *type* of software we are speaking of.
I never suggested anywhere in my post, to my knowledge at least, that what I said was correct. I plainly stated that this was an assumption on my part based on my past experience with computers, software, and various software licenses, and someone wishing to use the software under a certain license for a certain purpose should check into this to see what is really permitted. Since there has been previous concerns with the legality of the software issued by Berkeley, I was just pointing out things that *I* would consider if *I* were going to buy or otherwise obtain a piece of software for a specific purpose.

And also, since I am not a lawyer or anything, I can't say for sure, but "non-commercial" does sound like it would apply since the person would not be using it to actually sell the resulting program. They don't say that you can't provide it for free.
And I have just downloaded the source code and will try to come up with a Linux version, however my mother just passed away so it may take me a few days to get to work on it.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.