compile

[Carl Lowenstein]

> Date: Fri, 20 Jul 2001 15:23:54 -0700 (PDT)
> From: "M. Asim Rasheed" <asim at halcyon.usc.edu>
> To: The Penguin <kplug-list at kernel-panic.org>
> Subject: Re: compile
> In-Reply-To: <20010720222113.50798.qmail at web14301.mail.yahoo.com>
>
> ususally in the ./configure scripts , the path to different libraries is
> predefined (to the most common values). I suspect that the path for X11 on
> your system is different that what is given, by default, to the
> ./configure script.
>
> Asim
>
> On Fri, 20 Jul 2001, maveric maveriq wrote:
>
> > I'm trying to compile a program.  I'm doing  this
> > ./configure and everythings checks out unitl the last
> > thing and it tell me this;
> > 
> > checking for X... configure: error: Can's find X
> > includes.  please check your installation and add the
> > correct paths.

The whole purpose of ./configure is to automatically investigate your
system and find where things are.  The ./configure script looks in
several places (the usual suspects) to try to find the X11 includes.
Here is what a rather overblown configure script tries:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
  # Look for the header file in a standard set of common directories.
# Check X11 before X11Rn because it is often a symlink to the current release.
  for ac_dir in               \
    /usr/X11/include          \
    /usr/X11R6/include        \
    /usr/X11R5/include        \
    /usr/X11R4/include        \
                              \
    /usr/include/X11          \
    /usr/include/X11R6        \
    /usr/include/X11R5        \
    /usr/include/X11R4        \
                              \
    /usr/local/X11/include    \
    /usr/local/X11R6/include  \
    /usr/local/X11R5/include  \
    /usr/local/X11R4/include  \
                              \
    /usr/local/include/X11    \
    /usr/local/include/X11R6  \
    /usr/local/include/X11R5  \
    /usr/local/include/X11R4  \
                              \
    /usr/X386/include         \
    /usr/x386/include         \
    /usr/XFree86/include/X11  \
                              \
    /usr/include              \
    /usr/local/include        \
    /usr/unsupported/include  \
    /usr/athena/include       \
    /usr/local/x11r5/include  \
    /usr/lpp/Xamples/include  \
                              \
    /usr/openwin/include      \
    /usr/openwin/share/include \
    / \
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

If there is no success in any of these, maybe the file doesn't exist!?
Maybe the configure script that you (maveriq) have is not quite so
persistent.  Take a look at it for enlightenment.

    carl
-- 
        carl lowenstein   marine physical lab   u.c. san diego
                                          clowenstein at ucsd.edu