Solaris

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Prerequisite Software)
Line 27: Line 27:
 
== Prerequisite Software ==
 
== Prerequisite Software ==
  
 
+
It's time to install a '''lot''' of software:
 
+
Create a user (or the build system will complain that you're "root").  Create /home, and then create the user.  Let's call him 'moko'.
+
 
+
Before doing the su - moko, it's time to install a '''lot''' of software:
+
  
 
Try to install what you can from the package list in [[MokoMakefile]]
 
Try to install what you can from the package list in [[MokoMakefile]]
Line 57: Line 53:
  
 
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.
 
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.
 
  
 
== Notes ==
 
== Notes ==

Revision as of 23:45, 13 October 2008

Contents

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).

Using these directions for setting up the zone.

Prerequisite Software

It's time to install a lot of software:

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:

  1. apr-1.3.3/ -- for subversion
  2. apr-util-1.3.4/ -- for subversion
  3. bash-3.2/ -- the builtin cp doesn't take the -t option, the one in this newer bash does.
  4. diffstat-1.46/
  5. help2man-1.36.4/ -- build without NLS.
  6. git-1.6.0.2/ -- yum didn't have this.
  7. ncftp-3.2.2/ -- to make CPAN happy about Locale::gettext
  8. neon-0.28.3/ -- for subversion
  9. Python-2.6/ -- for the proper sqlite support. Yeah, the whole thing.
  10. sqlite-3.6.3/ -- for python's sake.
  11. subversion-1.5.3/ -- yum didn't have this.
  12. texi2html-1.64/ -- no package for this either.
  13. texinfo-4.9/ -- default version didn't have makeinfo
  14. make-3.81/ -- seriously
  15. tar-1.20/ -- again, seriously.

Actually, whenever you have the option, --disable-nls in the configure scripts seems to make life a lot easier.


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.

Notes

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 that user's .bashrc, pop in this line:

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

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

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).

Using these directions for setting up the zone.

Prerequisite Software

Create a user (or the build system will complain that you're "root"). Create /home, and then create the user. Let's call him 'moko'.

Before doing the su - moko, it's time to install a lot of software:

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:

  1. apr-1.3.3/ -- for subversion
  2. apr-util-1.3.4/ -- for subversion
  3. bash-3.2/ -- the builtin cp doesn't take the -t option, the one in this newer bash does.
  4. diffstat-1.46/
  5. help2man-1.36.4/ -- build without NLS.
  6. git-1.6.0.2/ -- yum didn't have this.
  7. ncftp-3.2.2/ -- to make CPAN happy about Locale::gettext
  8. neon-0.28.3/ -- for subversion
  9. Python-2.6/ -- for the proper sqlite support. Yeah, the whole thing.
  10. sqlite-3.6.3/ -- for python's sake.
  11. subversion-1.5.3/ -- yum didn't have this.
  12. texi2html-1.64/ -- no package for this either.
  13. texinfo-4.9/ -- default version didn't have makeinfo
  14. make-3.81/ -- seriously
  15. tar-1.20/ -- again, seriously.

Actually, whenever you have the option, --disable-nls in the configure scripts seems to make life a lot easier.


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.


Notes

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 that user's .bashrc, pop in this line:

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

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