This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: including winsock.h gives STATUS_ACCESS_VIOLATION in cc1


Hi!

Sunday, 03 September, 2000 Dr. Volker Zell Dr.Volker.Zell@oracle.com wrote:

DVZ> I tried compiling

DVZ>  openldap-2.0.0.tgz

DVZ> with latest cygwin-1.1.4 (including patch from Chris announced in one of his mails)

DVZ> When running configure like this:

DVZ>  ./configure  --with-gnu-ld --enable-shared=no --with-threads=no

DVZ> I get

DVZ> configure:4715: checking for winsock
DVZ> configure:4732: gcc -o conftest.exe -g -O2 -I/usr/local/include  -s conftest.c  1>&5
DVZ> In file included from configure:4721:
DVZ> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/winsock.h:26: parse error before `SOCKET'
DVZ> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/winsock.h:26: warning: data definition has no type or storage class
...
DVZ> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/winsock.h:431: parse error before `int'
DVZ> /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/winsock.h:433: warning: parameter has incomplete type
DVZ>       0 [main] cc1 9750 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
DVZ>   52035 [main] cc1 9750 stackdump: Dumping stack trace to cc1.exe.stackdump
DVZ> gcc: Internal compiler error: program cc1 got fatal signal 11
DVZ> configure: failed program was:
DVZ> #line 4720 "configure"
DVZ> #include "confdefs.h"
DVZ> #include <winsock.h>
DVZ> int main() {

DVZ>                         socket(0,0,0);
DVZ>                         select(0,NULL,NULL,NULL,NULL);
DVZ>                         closesocket(0);
DVZ>                         gethostname(NULL,0);
        
DVZ> ; return 0; }

DVZ> Any hints ??  Can anybody verify this ?

yes.  same  here.  as  a  workaround  you  can  either  add
#include <sys/types.h> before #include <winsock.h> in configure
(or more likely, you should do this in configure.in), or
comment #ifndef _SYS_TYPES_H_ (and respective #endif's) in winsock.h

as  for  internal  error in cc1, maybe someone with home-compiled gcc,
who  had  debug  info  in cc1 will make symbolic trace?

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]