E.2 Configuring or building XBoard fails due to missing header files, missing libraries, or undefined symbols.
Description
This article is from the GNU Chess and XBoard FAQ, by Tim Mann mann@pa.dec.com with numerous contributions by others.
E.2 Configuring or building XBoard fails due to missing header files, missing libraries, or undefined symbols.
Perhaps you have the X server and client programs installed on your
machine, but not the X header files and link-time libraries. If so, you
can run existing X programs, but you cannot compile a new X program from
source code. In this case the XBoard configure script will fail and will
tell you to look at this question in the FAQ. Many Linux distributions
put the headers and libraries in a separate package, which you might not
have installed. If you are using RedHat Linux, install the XFree86-devel
package. If you are using some other kind of Unix, ask your system
administrator where to find the X header files and link-time libraries.
If this is not your problem, read on.
The configure script for XBoard looks for X libraries and header files
in some common places. Sometimes it fails: If yours are installed in an
odd place, it may not find them at all. If you have more than one
version of X installed on your system, it may find the "wrong" one, or
occasionally it may find libraries from one version and incompatible
header files from another. You can work around these problems by telling
the configure script where the files are. For example:
configure --x-includes=/odd/place/include \
--x-libraries=/odd/place/lib
The directory named in the argument to --x-includes must have a
subdirectory "X11" that contains the actual .h files. That is, if your
X.h file has full pathname /odd/place/X11R6/include/X11/X.h, then you
must give the argument --x-includes=/odd/place/X11R6/include.
Some linkers have bugs that cause bogus error messages when you try to
link X programs. The configure script includes a workaround for a bug of
this kind that exists in some SunOS 4.x.x installations. See the FAQ on
comp.windows.x for more information about problems of this kind.
If all else fails, check whether anyone else at your site has been able
to compile any X programs on your system. Your X installation might be
buggy. If so, the system administrator at your site might know how to
fix or work around the problem.
Also see topic [E.1] .
Continue to:
My Books
