
	Solutions to some commonly encountered problems.

	1.q) When I run `make Test' I get the message:

		***complex division inaccuracy, check manually***

	1.a) Some compilers do not generate the best code for complex
	division. Most do. Some will pass or fail the test depending
	upon the level of optimization used. If RLaB fails this test
	do a manual check of complex division to verify that the
	answer is correct to within +/- machine-epsilon. If the answer
	is correct to within +/- machine-epsilon then it is safe to
	use RLaB.

	2.q) I get undefined symbols (like pow_zi) when the Makefile
	tries to link rlab?

	2.a) Undefined symbols like pow_zi are usually from the f2c
	libraries. If the Makefile found libF77.a and libI77.a, and
	these symbols are still undefined, then you probably have a
	Fortran compiler installed on your machine. Some vendors
	Fortran libraries will work OK. But, other vendors have
	gratuitously changed the libraries. 

	Try getting the latest version of the f2c libraries
	(research.att.com, or prep.ai.mit.edu). Or, you could write a
	Fortran interface and mail it to me :-)

	3.q) alloca is undefined?

	3.a) `make ALLOCA=alloca.o'

	4.q) When I run `make Test', it fails immediateley.

	4.a) The problem may be that your system does not declare
	strtod() in its header files. strtod() is used heavily by the
	scanner, and if it is not declared the compiler will think it
	returns int, which is not right at all. Fix: add

		#include <whatever_include_defs_strtod.h>

	5.q) When I run `make Test' RLaB reports an error in round()?

	5.a) Some platforms (HP for instance) have a rint() function
	in the system library, but it does not work. To fix: go into
	config.h and comment out the two lines:

		#define HAVE_RINT 1
		#define HAVE_RINT_DEC 1

	Then RLaB will uses its own rint().
