I had a similar problem doing a non-X cygwin build. configure wasn't properly
detecting Xpm because the compile would fail when Xpm.h included X11/Xlib.h,
which it doesn't do when FOR_MSW is defined. I didn't have time to investigate,
so I just started specifying --with-xpm on the configure command line.
configure then appears to assume the presence of Xpm and just checks to see if
FOR_MSW is needed.
Non-X Xpm detection definitely worked at one time. I have a short script I run
to execute configure with all the command line options I use. Xpm was being
detected just fine for a long time, then I had to go in and add the --with-xpm
option to my script. Unfortunately, I don't recall when it stopped working.
Rick
--- Craig Lanning <lanning(a)scra.org> wrote:
Andy Piper writes:
> At 09:13 PM 1/18/00 -0500, Craig Lanning wrote:
> >configure is not detecting the XPM library for a mingw32 build.
> >
> >After a little investigation, I found that the configure script needs to
be
> >modified so that it defines the symbol XPM_NUMBERS before trying to find
> >out which version of XPM is installed. Defining this symbol comments out
> >all of the XPM header except the version number declarations.
>
> This sounds suspicious to be. I would mistrust your XPM build.
It seemed a little suspicious to me, too, since it had worked before.
I don't have any X11 libraries or headers so when <X11/xpm.h> is read
and tries to include <X11/Xlib.h> and <X11/Xutil.h> it fails because
those files don't exist. Defining XPM_NUMBERS allows configure to
check the XPM version without having to know whether to define FOR_MSW
or not.
Craig
--
----------------------------------------------------------------------
Craig Lanning Principal Engineer
Logicon, Inc.
a Northrop Grumman company E-Mail: Lanning(a)scra.org
5300 International Blvd. Voice: 843-760-3246
North Charleston, SC 29418 FAX: 843-760-3780
USA
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com