GNU Go Installation Instructions
Get the most recent tar file from ftp.gnu.org or a mirror
(see http://www.gnu.org/order/ftp.html for a list).
Untar the sources, change to the directory gnugo-2.3.xx. Now do:
This makes a binary called src/gnugo. Now (running as root) type
to install gnugo in /usr/local/bin. This will also install the man page
gnugo.6 into /usr/man/man6.
There are two methods of using GNU Go. You may run it from the
command line by just typing:
but it is nicer to run it under X-Windows using CGoban.
Obtain the most recent version of CGoban from Bill Shubert's web site,
http://www.hevanet.com/wms/ . The CGoban version number MUST be 1.9.1
at least or it won't work.
Start CGoban. When the CGoban Control panel comes up, select `Go Modem.'
You will get the Go Modem Protocol Setup. Choose one (or both) of the
playsers to be ``Program,'' and fill out the box to the path to
gnugo. After clicking OK, you get the Game Setup window. Choose
``Rules Set'' to be Japanese (otherwise handicaps won't work). Set the
board size and handicap if you want. Click OK and you are ready to go.
In the Go Modem Protocol Setup window, when you specify the path
to GNU Go, you can give it command line options, such as --quiet
to suppress most messages. Since the Go Modem Protocol preempts
standard I/O other messages are sent to stderr, even if they are
not error messages. These will appear in the terminal from which
you started CGoban.
Other command line options can be listed by typing gnugo --help
-or- man gnugo from any terminal.
On one GNU/Linux machine compilation failed because it had an
incompatible /usr/include/curses.h (from BSD) which had
declarations inconsistent with those in /usr/include/term.h. The
symptom of this problem is compilation errors in src/moyo.c and
In this case, the correct curses.h was found in /usr/include/ncurses
and a correct compilation was obtained after changing
in src/moyo.c and src/showbord.c. If you have a problem with
errors in src/moyo.c and src/showbord.c caused by curses you
should try such a remedy first. If this doesn't work, you
shouldn't curse. Run configure --disable-color to turn off
the color option and compile again.