View source for Solaris

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Return to Solaris.

Personal tools

Building on Solaris

(Well, OpenSolaris)

Most of this is a war of inches, with the enemy using 10,000 paper cuts to bleed your soul dry.

Most likely, he'll win.

The opposition's key weapon is the excessive use of unnecessary features. Not even resulting in bloat, but just growing the dependency graph of installed software on the build system to make the entire thing incredibly sensitive to almost any difference between their build systems and yours.

Hence, why we're going to use a full Linux userland stack to do this. Atop of this, we'll have to upgrade components extensively to make this all work. You're going to hate all this.

But hey, at least you don't actually have to run Linux.

Note and Disclaimer

I'm still working on getting this all to work. Don't actually follow these instructions until I've claimed success. Until then, it's best an amusement to watch from the sidelines.

Onto the Point

After a few dead starts, the best way to build on Solaris is to use a BrandZ Linux zone, and install enough stuff into the CentOS-3 image to make it all work.

This is on a randomly, and partially, upgraded version of OpenSolaris Indiana (2008.5).

Use these directions for setting up the zone.

Prerequisite Software

It's time to install a lot of software. After you're done with this, you'll:

  1. Respect distribution maintainers more
  2. Loathe other software developers more

Try to install what you can from the package list in MokoMakefile

The rest by download, configure, and make. Here's what I've had to install so far:

Package Comments
apr-1.3.3/ for subversion
apr-util-1.3.4/ for subversion
bash-3.2/ the builtin cp doesn't take the -t option, the one in this newer bash does. You'll probably need this one-line patch
git- yum didn't have this.
ncftp-3.2.2/ to make CPAN happy about Locale::gettext
neon-0.28.3/ for subversion
openssl-0.9.8i/ for subversion. Install in /usr/local.
Python-2.6/ for the proper sqlite support. Yeah, the whole thing.
sqlite-3.6.3/ for python's sake.
subversion-1.5.3/ yum didn't have this.
texi2html-1.64/ no package for this either.
linux-2.6.18/ For the headers
texinfo-4.9/ default version didn't have makeinfo
make-3.81/ seriously
tar-1.20/ again, seriously.

As early as you can, build gettext and install it. Then setup LD_LIBRARY_PATH, /etc/, etc. before moving forward with the rest. Otherwise some of the configures will complain about

When they're installed, they'll go in the default prefix setting, namely /usr/local/bin. Put /usr/local/bin in as the first entry in your path.

Hacking up the system to make it work

Linux Kernel

Go into /usr/include, and

ln -s /usr/local/src/linux-2.6.18/include/linux .

Upgraded Python

In /usr/bin, rename python to old_python, and link /usr/local/bin/python here. This will break yum, so you'll have to change it back when you want to run that.

The new Bash

The build system will complain if you attempt to run it as root, even if it's the bullshit root in a container (it can't tell the difference). Create /home, and then create a user (say "moko") to run the build system. Also, edit /etc/shells and add /usr/local/bin/bash to the list. Finally, edit /etc/passwd and change moko's shell to /usr/local/bin/bash.

In both root's and that user's .bashrc, pop in these lines:

export PATH=/usr/local/bin/:$PATH export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

So that your new tool versions & shared libs will get picked up properly.

Runtime Library Setup

Also, add /usr/local/lib to /etc/ (in the zone, obviously), and do an ldconfig after installing gettext.