my local workspace fixes this, as follows:
Index: cygwin32.h
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/s/cygwin32.h,v
retrieving revision 1.14.2.15
diff -u -r1.14.2.15 cygwin32.h
--- cygwin32.h 2000/03/06 20:57:49 1.14.2.15
+++ cygwin32.h 2000/04/14 06:26:53
@@ -61,6 +61,9 @@
extern int cygwin32_win32_to_posix_path_list_buf_size(const char*);
extern void cygwin32_posix_to_win32_path_list(const char*, char*);
extern int cygwin32_posix_to_win32_path_list_buf_size(const char*);
+
+extern double logb(double);
+
# if CYGWIN_VERSION_DLL_MAJOR < 20
struct timeval;
struct timezone;
@@ -69,7 +72,6 @@
extern int gettimeofday(struct timeval *tp, struct timezone *tzp);
extern int gethostname (char* name, int namelen);
extern char* mktemp(char *);
-extern double logb(double);
extern void sync();
extern int ioctl(int, int, ...);
/* sys/stat.h */
@@ -107,6 +109,8 @@
# define MAC_CHARSET 77
# endif
#endif
+
+#include <windows32/defines.h>
#ifndef SPI_GETWHEELSCROLLLINES
#define SPI_GETWHEELSCROLLLINES 104
Andy Piper wrote:
At 11:32 AM 4/6/00 -0400, Craig Lanning wrote:
>I am trying to improve support for mingw (and, as a side effect,
>cygwin) in the configure script. Specifically, there are some
>#define's that are needed by the older version of cygwin, but are
>included in the newer snapshots and upcoming net release.
We need Martin' input on this. My gut fell is to create new headers -
syswinnt.h, syscommctrl.h, syswinspool.h etc which include the real header
but also provide definitions if they don't exist. There is precedent for
this but I'm not sure if Martin would advocate it. I don't like putting
every single #define in configure since it makes configure take a *really*
long time on cygwin.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/typing.html.