Correct/augment: boinc.berkeley.edu/solaris.php
Solaris 10 requirements: (tested on SPARC as of 12/28/2005 & should be the same on x86/x64)

Using: boinc_4.43_sparc-sun-solaris2.7.sh


- Requirements for the BOINC Client Seti program:


- gcc libs. Since the default installation of Solaris 10 comes with gcc 3.4.3 installed into /opt/sfw, just need to set:


LD_LIBRARY_PATH=/usr/local/lib:/opt/sfw/lib
export LD_LIBRARY_PATH



If you did not install the default/full ver of Solaris 10 and do not want the full ver of gcc for some reason, www.sunfreeware.com has packaged just the libs called: libgcc (I have not tested this with BIONC or seti)


Excerpt from www.sunfreeware.com as of 12/28/2005:
libgcc-3.3-sol10-sparc-local.gz This package includes the files and links

libgcc_s.so libstdc++.a libstdc++.so libstdc++.so.5.0.5
libgcc_s.so.1 libstdc++.la libstdc++.so.5 sparcv9

./sparcv9:
libgcc_s.so.1 libstdc++.a libstdc++.so libstdc++.so.5.0.5
libgcc_s_sparcv9.so libstdc++.la libstdc++.so.5

Since these files are part of the gcc package, you may not need to install it if you already have gcc 3.3 installed. This package is created because some programs will not run without these libraries - installs in /usr/local/lib.
---- end of excerpt ----



- Requirements for the BOINC Manager:

- Expat as of 12/28/2005, only the Solaris 9 SPARC pkg avail from www.sunfreeware.com, but OK to use.

expat-1.95.5-sol9-sparc-local.gz

- If you receive a message such as: "Error: wxWidgets could not open display" it's because the Manager is a GUI and requires X-Windows (X-Win for MS Windows if running from PC, etc.) or graphic console, etc. I did not have to "install" wxWidgets. You can use xhosts for testing, if you are having an access/authentication issue, but xhosts is not recommended for security purposes. Excerpt from Solaris 10 documentation at docs.sun.com: Use the xhost program to change the host-based access list in the server. You can add hosts to, or delete hosts from the access list. If you are starting with the default configuration—an empty host-based access list—and use xhost to add a machine name, you lower the level of security. The server allows access to the host you added,as well as to any user who specifies the default authorization protocol. See Host-Based Access [f]or an explanation of why the host-based access control mechanism is considered a lower level of security.


- Once the expat error is gone, you will receive another error that it's missing iconv libs. So, get and install iconv. This is installed in /usr/local so the previously set LD_LIBRARY_PATH above will find the iconv libs

libiconv-1.8-sol10-sparc-local.gz from www.sunfreeware.com

--- that's it----

Comments: Everything seems to be working now.


BTW, I have it installed in a Solaris 10 Local Zone/Container (ie: not the Global/default zone) running as an ordinary user (not root) and both client and manager are working. Next test is to use Solaris 10's SMF (service management facility) to manage the BOINC process (start at boot time, stop, restart, monitoring the app with restart if it dies, etc.), and then limit the user running BIONC to the Least Privileges possible for the tighest security. This is the way I was running the non-BOINC seti on Solaris without problems.

I will write David Anderson a mail to add the requirements to the solaris.php.
Btw. do you know, where wxWidgets binaries for solaris could be downloaded.

---

I will write David Anderson a mail to add the requirements to the solaris.php.
Btw. do you know, where wxWidgets binaries for solaris could be downloaded.

I did not download or install wxWidgets. It works without showing this error message if the system can open a GUI display. It's an error message that says it can't open the display/window. The message does not say it can't find wxWidgets.

If one can (for example) run /usr/openwin/bin/xclock and actually see a GUI clock popup on your monitor in a little window, then one should not be getting the wxWidgets message. If xclock fails to work the user has an X-Windows issue of either access/authentication, not running on a graphic console, and/or not using a compatible X-Windows protocol such as basic telnet/ssh, etc. (or a combination of all of these issues)

If you are seeing another wxWidgets type error message, please let me know what it is.