On Thu, May 22, 2008 at 05:48:14PM -0400, Mike Marchywka wrote: >> From: [EMAIL PROTECTED] >> Date: Thu, 22 May 2008 16:15:16 +0100 > >Thanks. If you are interested, let me try to give a chronology of follow on >events as best as I can >reconstruct: > >1::::::::::::::::::::::::::::::::::::::::::: >> Wrong place to look, surely? >> >> http://cygwin.com/cgi-bin2/package-grep.cgi?grep=sys%2Fsockio.h > >Oddly enough, that helped :) >OK, so I copied sockio.h and also needed ioccom.h. Just to be clear, > >http://cygwin.com/cgi-bin/cvsweb.cgi/src/newlib/libc/sys/linux/sys/ioccom.h?cvsroot=src > >my install is messed up so I'm not sure this problem applies to anyone else >but I'm just being complete incase it matters.
As the sys/linux above implies, this is linux-specific code. It has no bearing for cygwin. >2::::::::::::::::::::::::::::::::::::::::::::::: > >Then, I encountered a define problem. This seems to have occured elsewhere >so I thought I would post the issue with definition of ssize_t: > >http://code.google.com/p/xdelta/issues/detail?id=56 > >This turned out to be flagged with __CYGWIN__ and also easy to fix in the >makefile. > >3:::::::::::::::::::::::::::::::::::::::::::::::::::::: > >But, then I had a missing definition for IFF_POINTOPOINT which does seem to be >an issue with cygwin. According to this, the symbol should be defined in if.h: > >https://www.linux-foundation.org/dbadmin/browse/headgroup.php?cmd=list-byheadgroup&HGid=437 > >my if.h needed to be modified, > >#define IFF_LOOPBACK 0x8 /* is a loopback net */ >// >#define IFF_POINTOPOINT 0x10 /* mjm, */ >// >https://www.linux-foundation.org/dbadmin/browse/headgroup.php?cmd=list-byheadgroup&HGid=437 > >#define IFF_NOTRAILERS 0x20 /* avoid use of trailers */ > >4: :::::::::::::::::::::::::::::::::::::::::::: >Next, a problem with INET6_ADDSTRLEN16. I found this and implemented the >suggestion, > > >http://viral.media.mit.edu/peers/peers-win.html > >#if defined(__CYGWIN__) >#define INET_ADDRSTRLEN 16 >#define INET6_ADDRSTRLEN 46 >#endif /* __CYGWIN__ */ > >which again seemed to work but I have no idea what other problems may turn up >if this isn't right. > >5:::::::::::::::::::::::::::::::::::::::::::: > >Then I finally encountered a big link problem and determined that some >pieces were built with and without -mno-cygwin. I was finally able to >stop it from complaining by grepping all the libraries for the missing >symbols and just randomly adding stuff but, duh, the executable >wouldn't run. I can probably figure this out but I've never built >anything with -mno-cygwin before so it will probably take a while. Sorry but you're very confused by this point. Compiling with -mno-cygwin means that you can't use ANY cygwin headers. You won't be able to create an executable which works this way. When Dave said "...cygwin doesn't supply or support <sys/sockio.h>" he wasn't kidding. It isn't supplied and copying it from a random source and randomly making changes is not going to work. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
