72.5 Known Problems of the Configure Process

If make complains ``Do not know how to make xyz'' but xyz is an existing file, it is likely that the dates of the files were not extracted properly (Alpha-OSF machines are prone to this). Call

touch * cnf/* src/*
from the main GAP directory (this ought to reset the date of all relevant files to ``now'') and try again.

Rarely the configure process does not find out properly about the ``inline'' compiler command. If you get error messages that complain that ``inline'' is unknown, edit the file config.h in the bin/target subdirectory and replace the line

/* #undef inline */
by
#define inline
and then try to compile again.

The configure script respects compiler settings given in environment variables. However such settings may conflict with the automatic configuration process. If configure produces strange error messages about not being able to run the compiler, check whether environment variables that might affect the compilation (in particular CC, LD, CFLAGS, LDFLAGS and C_INCLUDE_PATH) are set and reset them using unsetenv.

Some users reported problems with make, while the GNU version gmake worked. Thus if problems occur you should try gmake instead if it is installed on your machine.

[Top] [Previous] [Up] [Next] [Index]

GAP 4 manual
February 2000