Chandler on Gentoo Build Notes

Building Chandler on Gentoo is relatively straightforward, as the build process is largely self-contained. You can build by hand or via ebuilds, examples of which are attached to this document (one for 0.5.02 build, and another for a live subversion build).

Prerequisites

The primary prerequisites are:

• GCC >=3.4.2 built with Java/GCJ support
• GTK2

As of 2005-04-24, Gentoo's standard GCC is 3.3.5. A >=3.4.2 GCC can be built as a "SLOT" build which does not interfere with the standard installation. To do so, follow these steps:

1. Edit /etc/make.conf and add "gcj" to the USE variable.
2. Edit /etc/portage/package.keywords and add these two lines:
   • >sys-devel/gcc-3.4.0 -*
   • sys-libs/libstdc++-v3 ~x86
3. As root, run emerge >=gcc-3.4.2

The exact steps needed will change as Gentoo package defaults change. GCJ USE support will always be required.

Run gcc-config -l. If the selected version is not 3.4.2 or above, you will need to change to a later version during the build. Find the number corresponding to a >3.4.2 build and type gcc-config NUMBER. You can switch back when you are done.

You can also download and build a GCJ-enabled GCC by hand if desired.

Building by hand

If you wish to build by hand, as of 2005-04-24, the Chandler build process requires a GCJ_HOME variable be set which is assumed to be the root of a GCC installation built with Java support. For using a Gentoo-provided GCC, you must "fake" a GCJ_HOME. Build one using a procedure like this:

1. mkdir -p /tmp/gcj-home/bin
2. cd /tmp/gcj-home
3. ln -s `gcc-config -L` lib
4. cd bin
5. for i in `gcc-config -B`/*; do ln -s $i `basename $i`; done
6. ln -s gcj-jar jar

See the GettingChandler page for more information about how to obtain a tarball of the source. Any type of source should work, including a release tarball, a snapshot tarball, or a subversion checkout. Once the source is obtained, see the BuildingChandler^? page for source build instructions.

Building via ebuilds

Download the appropriate ebuild and place it into your PORTAGE_OVERLAY directory (as specified in your /etc/make.conf, or go research how to configure that). The ebuilds should end up in a location like /usr/local/portage/app-office/chandler/chandler-0.5.02.ebuild.

After this is done, run cd /usr/local/portage/app-office/chandler && ebuild chandler-0.5.02.ebuild digest to create the necessary support files.

Once the ebuild is registered, simply use emerge chandler (or emerge chandler-svn) as root and the build process will proceed. An executable startup script will be placed in /usr/bin/chandler.

The ebuild files are available here:

• chandler-0.5.02.ebuild: Lightly-tested ebuild to build Chandler 0.5.02
• chandler-cvs-0.01.ebuild: Lightly-tested ebuild to build Chandler from OSAF CVS HEAD; DEPRECATED - USE SVN EBUILD INSTEAD
• chandler-svn-0.01.ebuild: Lightly-tested ebuild to build Chandler from OSAF SVN trunk