Solaris and OpenSolaris are operating systems that are available for free. In addition, OpenSolaris is released under the CDDL, a FOSS license, by Sun Microsystems. Whilst Solaris has its roots in BSD, it is mostly SysV. Solaris 10 is certified UNIX SUSv3. KDE4 runs on this operating system.
The KDE Project on the OpenSolaris site is intended to be the definitive source of information, but this page on TechBase is intended to collect information, porting and compilation guides, etc. Since TechBase is a wiki, this is much easier than going through the OpenSolaris editing process.
Status: For an overview of the remaining issues, see the KDE4 on Solaris status page. It lists showstopper bugs and issues with dependencies.
OpenSolaris: Building on OpenSolaris is covered on the OpenSolaris-specific page.
This page is concerned with instructions on how to build it all.
!!! This page is not outdated. There's not much movement in the repositories mentioned here, because of issues between Solaris 10 and KDE > 4.1.4, mostly around things like xcb which are not native to Solaris 10
Solaris and OpenSolaris are trademarks of Sun Microsystems, Inc.
This page is about KDE4 (the KDE 4.1.4 branch; we are aiming for having KDE4.1.4 fully functional on Solaris) on Sun Solaris S10U5/U6 or Solaris Nevada (Express) B101, running on both amd64 or SPARCv9 hardware and compiled with Sun Studio 12.
No other KDE releases, operating system versions, compiler version (ie, not Studio 11 or Sun Studio Express) or hardware platforms are the target of this project, simply because the core contributors to the project do not have them or the time to work on them.
That's not to say it will not necessarily work; people have and continue to contribute work for older hardware platforms (32-bit only like i386[P3/Athlon]). You can probably run the binaries produced by the project on other OpenSolaris releases, even OpenSolaris 2008.11 or 2009.06, but you're on your own.
On your own, that is, unless you register for Techbase and add your comments on what needed doing and what was problematic somewhere below.
We are concentrating on 4.1.4 because of issues surrounding dependencies of xcb in KDE 4.2, and it is highly unlikely that Solaris 10 will ever support xcb because of the fundamental change in the OS that would have to take place to support xcb.
The core team for KDE4 on Solaris is Adriaan de Groot, Lukas Oboril, Stefan Teleman. We'd like to thank Edward O'Callaghan, Ben Taylor and Mark Wright for their help in particular.
We don't have much in the way of documented KDE4 *use* on Solaris nor many reports of bugs found in daily use of the below KDE4 packages on http://bugs.kde.org/ . Thus we welcome any contributions though either bug reports, the repo or by email.
|The Techbase documentation gets out of date quite quickly. Do not follow it blindly; step into the IRC channel or on to the mailing list for more details or help with issues.|
Getting KDE4 on your Solaris machine requires the following:
You can use either Solaris 10 update 5/6 (S10U5 or S10U6) or Solaris Express (Nevada build 101 or 110 -- these two versions run on our build machine and on at least one developer's desktop). Other versions of the operating system might work, but there are no guarantees and probably not much sympathy either; OpenSolaris 2008.5 is downright broken as a development platform.
Studio 12 There is a command line install and a GUI. With the GUI, you can choose not to patch immediately (select the Advanced Options tab when you get to the install options, and un-select "Install Product Patches"). If not using the GUI, then use the batch installer as such (set -a <parm> as required):
./batch_installer -d /opt/SUNWspro -a intel-S2 --copy-sysprep --accept-sla --no-prodpatch
The reason to not patch immediately, is that you're going to have patch Studio 12 after installing, and there's no sense carrying around an extra 400MB in saved patches because the Studio 12 distro already has some older patches included in the distribution. Using Patch Check Advanced (PCA) works well on both S10 and SXCE to handle patches for Studio 12.
If you are running OSOL2008.11 or OSOL2008.05, then you will need to select the download Studio 12 *tarball* from the Sun Download site. The packages will add on OpenSolaris, but patchadd *doesn't* work, so you will *not* be able to update the packages for bug fixes on the compiler. An alternative would be to rsync /opt/SUNWspro from a working Solaris 10 or Solaris express system to the Open Solaris system. This may be easier in the long run if you have this configuration, since you'll patch S10 or SXCE, and then just rsync to the OSOL box.
Also patch your OS with (again, these are listed on the SS12 patches page):
You can check with CC -V if you are up-to-date for the 124864 patch and cc -V for the 124868. Those are the most important ones.
FOSSboost will fail as follows:
vesta% tail /tmp/FOSSboost.log pkgbuild: + chmod 755 Solaris/patch.sh pkgbuild: + bash -x ./Solaris/patch.sh boost pkgbuild: + '[' '!' -f configure ']' pkgbuild: + echo '# Checking if pyport.h is sane ... must not redeclare gethostname.' pkgbuild: # Checking if pyport.h is sane ... must not redeclare gethostname. pkgbuild: + test -f /usr/include/python2.4/pyport.h pkgbuild: + grep '^extern int gethostname' /usr/include/python2.4/pyport.h pkgbuild: extern int gethostname(char *, int); pkgbuild: + exit 1 pkgbuild: Bad exit status from /var/tmp/pkgbuild-edwardoc/pkgbuild-tmp-1.8081 (%prep)
|In /usr/include/python2.4/pyport.h , there's a gethostbyname prototype; it's wrong. Delete it entirely for building (simply commenting it out is not sufficient as the make system will check for its presence with a grep and if it is present even in comments the build will fail).
The line reads as:extern int gethostname(char *, int);
|If you would like to build FOSSnas as a dep, It will fail unless you copy the following files into /usr/X11/lib/X11/config/ More info here; cat /tmp/FOSSnas.log|
* Fixed in SNV103: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6763798
* Here is a workaround:
[edward@SXCE-Workstation]:/export/home/edward:~>uname -sv SunOS snv_99
If you don't do this step you will end up with the following error : "FOSSnas | FAILED | pkgbuild build failed"
/usr/bin/bunzip2 -cd xorg-cf-files-1.0.2.tar.bz2 | tar -xvf -
N.B. Please check if a later version is out in : http://dlc.sun.com/osol/jds/downloads/cbe/
cd ~ ; mkdir CBE1.7 ; cd CBE1.7
/usr/bin/bunzip2 -cd desktop-cbe-1.7.0-rc1-x86.tar.bz2 | tar -xvf -
/usr/bin/bunzip2 -cd desktop-cbe-1.7.0-rc1-sparc.tar.bz2 | tar -xvf -
`cd` in and follow the README/INSTALL file.
|If you didn't tell CBE where you want to build the code, it will try to put it under /opt/dtbld. That really won't work because /opt/dtbld is owned by root. Modify ~/.pkgbuildmacros and fix %_topdir to some writable directory that you want to build the code in. Most folks use ~/packages. You can also route the BUILD logs to a directory specified by: ~/.pkgtoolrc and tell "logdir:" where to put it. (~/packages/BUILDLOGS seems reasonable)|
Simply; cd ~ ; mkdir KDE4.X.x ; cd KDE4.X.x/
cd ~ ; mkdir KDE4.X.x ; cd KDE4.X.x/
N.B. The above is also for contributing back (which this mail message is all about). The *-specs-dev repo is public and writable (over https). So we welcome you too can push fixes back on to it; A review will happen before things end up in *-specs.
cd kde4-specs/ ; hg up ; cd specs/
This will now go off and build KDE4 and enything else needed as SysV packages. Come back in about 24h depending on your hardware.
FOSSnas | PASSED | FOSSncurses | PASSED | FOSSopencdk | PASSED | FOSSopenldap | PASSED | FOSSpcre | PASSED | FOSSphonon | PASSED | FOSSqimageblitz | PASSED | FOSSqt | PASSED | FOSSreadline | PASSED | FOSSsoprano | PASSED | FOSSsqlite | PASSED | FOSSstdcxx | PASSED | FOSSstrigi | PASSED | FOSSxprop | PASSED | KDEbase-apps | PASSED | KDEbase-runtime | PASSED | KDEbase-workspace | PASSED | KDEdt-integration | PASSED | KDElibs | PASSED | KDEpim | PASSED | KDEpimlibs | PASSED | KDEsdk | PASSED | FOSSlibiconvwo | PASSED | FOSSgettextwo | PASSED | FOSScyrus-saslwo | PASSED | FOSSmit-kerberos5wo | PASSED | FOSSopenldapwo | PASSED |
As usual, the IRC channel is a good place to start, but you must be able to pastebin compilation errors in order to get any help. The IRC channel is never too busy. #kde-solaris on irc.freenode.net . However, keep in mind that IRC is a live medium and it may not be the best place to ask questions. The mailing list kde-discuss at opensolaris.org is much more patient.
Also, you are expected to do your homework. Compiling KDE4 on Solaris is not for the faint of heart and you really need to know your way around compiling stuff and dealing with system software installation; otherwise you will be quickly ignored.
A basic install script has been provided to do as much validation as can be done to make sure accounts, privileges, space requirements are satisfied to install the binary packages for KDE4 for Solaris.
The install script has several options:
You must set SRC_DOWNLOAD to a location that has 3GB of free space, not including the requirements for 2GB on /opt.
There is an option to download, unroll, and remove the tarball and pkg dir after install which minimizes the need for keeping it all local. This is done by editing the following variables in the script as such:
The script was tested locally, and other than not downloading the tarballs to the local system, the script stands up a beautiful KDE4 install for Solaris 10. You are expected to follow the instructions the script give you if you are missing accounts or privilieges.
No warranties, implied or otherwise. I'm doing this just because I'm hoping other folks will help test KDE4 and be able to report bugs. It does take about a day to build KDE4 on a Quad core X64 box as I've packaged it, so the build is not trivial.
This is KDE-4.1.3 for Solaris 10/X64. (if you choose to load it on SXCE or OSOL, comments about it's functionality or things being borked will be ignored... )
The install script is maintained and located (and will be updated) at http://solaris.bionicmutton.org/PKGS/S10-x64/Install-s10-x64-kde4.sh
There are some local variables in the script, which will allow you to change some of the behaviors, such as download all, but don't install, or download each package, install it and remove the downloaded package.