We had a voulunteer for doing the port, but I haven't heard of him for months now. Apparently he ran out of free time for that (like we all do...). Currently there is done quite some work on the code of BOINC as well as on the science code. Maybe we'll start another attempt when the codebase is more stable again. But the priority for new ports is rather low for now.
BM

SPARC Solaris Einstein@Home?
)
I just built a Solaris/SPARC version of the new Albert App, which seems to run well on Solaris 7 and 10 (and thus it should on 8 and 9, too). We plan to release it after some testing. Our SPARCs are somewhat slow, so this may take a while. Stay tuned.
BM
BM
The Solaris Einstein@Home app
)
The Solaris Einstein@Home app that Bernd built is now being distributed (command line version only; graphical version coming soon). Please use this thread to report success or problems.
Bruce
The stock clients all request
)
The stock clients all request sparc-sun-solaris2.7 platform, as they are built on a Sol7 so they should run on all systems from then on. If you compile your own client, you are advised to use --build=sparc-sun-solaris2.7 as additional configure option, so the client will report the same platform.
Due to an old build process (which has been improved since then) the old 4.19 links to shared libraries that are not present on all systems (to say the least), in particular libstdc++.so.3 and libgcc_s.so.1. If you have a gcc installed, you can create a symlink named libstdc++.so.3 to your version of libstdc++.so.
I am running the stock recommended 4.43 client without problems.
BM
BM
RE: Hi... I'm very happy to
)
Which client are you using? I don't know about BViewer, but what do you get when you grep client_state.xml for "fraction_done" on the machine in question?
BM
BM
RE: RE: But the
)
I am aware of the rather poor performance and am working on optimizations. I was happy to get something working at all. The App has been compiled with gcc-3.3 on a Solaris7 system, for now with -O3. I'm investigating and expect to improve the performance significantly.
BM
BM
RE: RE: I am aware of
)
AFAIK the -ftree-vectorize doesn't make sense without the extensions (i.e. is ignored). Also it doesn't help much with our code, at least the 4.0.1 on x86 didn't recognize our loops as being vectorizable.
Hasn't gotten easier yet...
BM
BM
RE: AFAIK the
)
Sorry, must have been gcc 4.0.2.
BM
BM
RE: bit now with 2 projects
)
Hm, I'm tempted to suggest a newer client, but I'm aware there is no such available from BOINC for download - you'll either have to roll your own or look for other friendly crunchers who did that for you...
What happens if you set your preferences to "use no more than 1 CPU"?
BM
BM
RE: I got another problem
)
What version of Solaris are you running this on? Are the patches up-to-date?
Anybody else seen this?
It might be a problem with the Core Client, or a with shared library (pthreads?).
BM
BM
RE: SPARC optimizations
)
Thanks, this looks useful. However I just checked again - -mcpu=ultrasparc doesn't gain anything with the current code. I expect some speedup once I get the autovect feature of GCC 4 to recognize our loops as vectorizable and use vis, but this may take some time.
BM
BM