Swarm: platforms

Wiki main page
Swarm main page
Software main page
Stable release
Development snapshot
License
Platforms
Prior releases
Documentation main page
Doc set & reference guide
User guide
FAQ
User support email list
Applications & contrib code
Applications
User-contributed code
Release Management
Checklist

This page has archived information on running Swarm on more exotic platforms.

For information on running Swarm on Linux, Windows, and Macintosh:</br> go to the stable release page.

HP/UX

Swarm 2.0 is known to run on HPUX 9, 10, and 11. Java users of Kaffe will need this [27]libltdl patch. Also, to avoid a linker bug, build gcc-2.95 with this [28]compiler patch to gcc/objc/objc-act.c

IRIX

We have reports from some successful users of Swarm on SGIs in the following configurations:

SGI Origin 200, IRIX 6.4, GCC 2.7.2.2 w/old_ld configured for IRIX 5.3
IRIX 5.3, GCC 2.7.2.1
IRIX 6.4 GCC 2.8
IRIX 6.5 GCC 2.95.1

Note that IRIX users need to install libffi, and configure Swarm with the --with-ffidir option.

Solaris

Here's how to compile the CVS version of Swarm on Solaris 2.8. Note that this was recommended as there are problems with compiling swarm-2.2 (see Swarm support archives). This applies to the CVS version as obtained on 12 June 2006. You need the following:

autoconf/automake/libtool: These should be installed in the same directory. Versions 2.59, 1.9.6, and 1.5.22 respectively are known to work.
binutils, fileutils, gperf, emacs, m4, GNU sed and GNU tar. Versions 2.14, 4.1, 3.0.1, 21.4a, 1.4.2, 4.1.4, and 1.15.1 respectively are known to work. GNU tar may only be necessary if you are building gcc.
A version of gcc configured to use GNU ld (in binutils), and GNU make (versions 4.1.0 and 3.80 respectively are known to work).
CVS
The standard Swarm needed software: Tcl-Tk/BLT (versions 8.4.12 and 2.4z respectively are known to work), which should be installed in the same directory (call this $tcltkblt; XPM (version 3.4k is known to work) in directory $xpm; libpng and zlib (versions 1.2.8 and 1.2.3 are known to work) in directories $png and $z; and JDK if required (1.5 known to work) in directory $jdk. The installation on which this is based did not involve HDF5.

Note that Tcl/Tk seems to need a copy of libgcc_s.so.1 accessible from your LD_LIBRARY_PATH (see the Sunfreeware site). Your LD_LIBRARY_PATH should also point to $tcltkblt/lib, $xpm/lib, $png/lib and $z/lib when building Swarm. Your PATH should point to the bin subdirectory of the relevant tools mentioned above.

Assuming the cwd is that in which your compilation and build is to take place, and that $swarm contains the desired installation location, the commands to build swarm would be something like:

cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/swarm co swarm
# obtain the CVS version of Swarm

mv swarm swarm-cvs
cp -r swarm-cvs swarm
# keep the CVS copy pristine in case of problems!

cd swarm
./autogen.sh
# create configure script

cd ..
mkdir build-swarm
cd build-swarm
# build in separate directory from source

../swarm/configure --prefix=$swarm --enable-shared --with-gnu-ld --with-x \
   --with-jdkdir=$jdk --with-tcldir=$tcltkblt --with-tkdir=$tcltkblt \
   --with-bltdir=$tcltkblt --with-zlibdir=$z --with-pngdir=$png \
   --with-xpmlibdir=$xpm/lib --with-xpmdir=$xpm --x-includes=/usr/include \
   --x-libraries=/usr/lib
# You may want to configure differently than this, but bear in mind the
# following:
#
# --enable-shared is necessary if you want javaswarm to work -- you can ignore
#   comments in some of the documentation about having to configure without
#   shared libraries in Solaris.
#
# --with-x --with-xpmlibdir --withxpmdir --x-includes and --x-libraries are 
#   all needed to stop configure choking on XPM (or so I found after much
#   trial and error).

make
make install

The Swarm Support archives contain more information on the shared libraries and javaswarm.