Installation Problems.


The configure script in the src directory tries to solve most of the
problems that could occur.  It searches for missing include files,
compiles a program to remove prototypes or creates missing g++ libraries.
Since we don't have access to every type of computer system, we can't tell
if the installation will fail on an unknown system. If it does, please
report the problems and how you solved them.  Here are possible
solutions if the installation fails:


Chooses the wrong compiler.

	The configure script chooses by default the gcc/g++ combination
	if they are available.  If this combination fails for some
	reason, you can use the variables CC and CXX to choose a different
 	compiler. For instance,

		./Install CC=cc CXX=CC

	uses `cc` as C compiler and `CC` as C++ compiler.  If you do this,
	you need to remove the object files in the src directory because
	the compiler most like uses different symbol names.

Can't find the correct X11 include and library directories.

	If the configure-script uses the wrong X11 files, you can
	specify the include directory with INCLUDE and the library
	directory with LDLIBS. For instance,

		./Install INCLUDE=-I/usr/X11R6/include

	uses the X11 include files from /usr/X11R6/include, while
	
		./Install LDLIBS=-L/usr/X11R6/lib

	uses the X11 libraries from /usr/X11R6/lib. A different solution
 	would be adding /usr/X11R6/bin to your PATH as first directory.
	The configure script tries to find include and library directories
	by replacing 'bin' by 'include' or 'lib' in you PATH variable.


Missing include files

	If your system misses one or two include files, you can create
	empty include files in the src directory and hope that the
	include files didn't contain anything special. For example,
	if the file "sys/stat.h" is missing, you can use the following
	sequence to create that file, and compile again.

		mkdir src/sys
		touch src/sys/stat.h
		./Install INCLUDE=-I.

Missing g++ libraries.

	Sometimes g++ is available but the g++ libraries are missing.
	The configure script tries to solve these problems by creating
	dummy libraries, since the libraries are not really needed.
	If this fails for some reason, you could try to make these
	dummy libraries yourself, that is, create a library with

		ar cq src/libg++.a src/debug.o
		ln -s libg++.a src/libstdc++.a
		
	and rerun ./Install.


Socket library should be added.

	The configure script tries to decide if the socket library should
	be added and might take the wrong decision by not adding it.
	If it should be added, call Install with

		./Install LDLIBS="-lsocket"


