Platforms that Gubby has been tested on

        http://gubby.sourceforge.net

        This document contains platform-specific notes on running Gubby, as
        well as a list of platforms that have been reported to compile Gubby
        straight out of the box.

Note

        These are the results from compiling on the Sourceforge compile farm,
        and really all that matters is that you have a working system with
        some fairly working C++ compiler, STL and a curses library.

        In other words, if you have e.g. Debian 2.2 (which I couldn't get to
        work below because the STL std::vector function isbroken) and
        install the newest glibc++ (e.g. v3), then you'll most likely get
        Gubby to compile with no problems.

Gubby 0.5.5

	Should compile out-of-the-box as for Gubby 0.4.2 (see below).
	Some systems with old STL libraries / GCC versions may have to
	build like this:  COPTS=-DUSE_STRSTREAM make

	Verified systems include (only tested for gubby 0.5.1):

	Linux 2.4.19 (Debian 2.2), GCC 2.95.2 (make COPTS=-DUSE_STRSTREAM)
	Linux 2.4.18 (Redhat 7.3), GCC 2.96 (make COPTS=-DUSE_STRSTREAM)
	Linux 2.2.20 (Debian 3.0), GCC 2.95.4 (make)
	FreeBSD 5.0 (CURRENT), GCC 3.2.1 (make)
	Linux 2.4.18 (Debian 3.0), GCC 2.95.4 (make)
	Sun Solaris (8) (SunOS 5.8), GCC 2.95.3 (gmake)

	At the time of writing, the Sourceforge.net compilefarm lacks the
	FreeBSD-stable (4.7), so I haven't verified that Gubby compiles
	out-of-the box on that.  Anyway, it shouldn't be much of a problem to
	compile Gubby (at least with GCC) when you have a working STL library and
	curses installed.  The s-lang curses wrapper (slcurses) setting found in
	the Makefile should not be used, as it's just there for testing purposes
	(meaning: it won't work).


Gubby 0.4.2

	Compiles out-of-the-box on the following platforms

        Cygwin (Windows NT/2k), GCC 3.2    (x86)
        FreeBSD 4.7 (STABLE),   GCC 2.95.4 (i386)
        FreeBSD 5.0 (CURRENT),  GCC 3.2.1  (x86)
        Linux 2.2 (Debian 3.0), GCC 2.95.4 (Alpha)
        Linux 2.4 (Debian 3.0), GCC 2.95.4 (Cerfcube - SA1110)
        Linux 2.4 (Debian 3.0), GCC 2.95.4 (Sparc - Ultra60)
        Linux 2.4 (Redhat 7.1), GCC 2.96   (IBM Websphere V 5)
        Linux 2.4 (Redhat 7.1), GCC 2.96   (x86)
        Linux 2.4 (Redhat 7.3), GCC 2.96   (x86)


Platforms with compilation problems

        COMPILES, BUT CAN'T FIND libncurses.so.5 WHEN EXECUTING Sun Solaris
        (SunOS 5.8), GCC 2.95.3 (Sparc - R220)

        Linking with curses instead of ncurses fails because it can't find
        the functions wattr_off and wattr_on.  This is a classic curses
	problem on SunOS, it seems, but I haven't found a way to fix it
	yet.  Any clues would be helpful.


Cygwin
        Compiles nicely with GCC 3.2 and ncurses.  Note that the curses
        controlled terminal does not seem to work well whenTERM=cygwin.

        Try setting to TERM=xterm og TERM=xterm-color, or perhaps other,
        more appropriate values, which seem to yield a better result.


getopt_long() vs getopt()

        It seems only Linux has a getopt.h that defines the function
        getopt_long().  Therefore, for portability, I've decided for the time
        being to only use getopt(), which means that long options are not
        supported anymore.  In some future version of Gubby, I'll move on
	to using autoconf, so that things like this will be easier.


$Id: PLATFORMS,v 1.10 2004/12/16 16:18:45 cslsublevel3org Exp $