this is my wish...

Actually, it would be nice if the Boinc & Seti clients would even compile
under OpenBSD 3.6/Sparc64. I've found lots of suggestions, and many
have helped such that Boinc will now compile, but the Seti Client is not
very portable code. The so called "public" cvs versions appear to be
missing lots of files

> Actually, it would be nice if the Boinc & Seti clients would even compile
> under OpenBSD 3.6/Sparc64. I've found lots of suggestions, and many
> have helped such that Boinc will now compile, but the Seti Client is not
> very portable code. The so called "public" cvs versions appear to be
> missing lots of files
>

I can't compile under openbsd 3.6/sparc64.
Did you use the cvs-tree or the boinc-4.11.tar.gz (archive build)?
The current archive build didn't work.

./configure >> work (with warnings)
make >> not work (because cannot find some files)

---

>
> I can't compile under openbsd 3.6/sparc64.
> Did you use the cvs-tree or the boinc-4.11.tar.gz (archive build)?
> The current archive build didn't work.
>
> ./configure >> work (with warnings)
> make >> not work (because cannot find some files)
>

The rumor is for boinc, you should do a
./_autosetup
./configure
make
make install
and it is suppose to work ,,, urp.

TarBall , cvs public, or cvs current, and have picked a few different dates ... all the same.
make does not work, it expects a gmake, and you'll need to edit a few .h files that seem to
think only MS, or Linux exist. I've have to change a dozen or so things, but each release
seems a little worse. The seti client ... more so. I was going to spend some time on it next
year to see what it really takes to fix it.
In the dev/opt mailing lists there have been some discussion, but little seems to be going
on about some of the root causes of these issues.