bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch for Cygwin environment


From: Federico Montesino Pouzols
Subject: Re: Patch for Cygwin environment
Date: Tue, 18 Mar 2003 20:34:41 +0100
User-agent: Mutt/1.5.3i

        I have just committed the patch to CVS. A new EGREP check has
been added in order to check for socklen_t in cygwin/socket.h, in case
it is not defined in sys/socket.h. Let me know if there is any problem
with this modification.

On Sat, Mar 01, 2003 at 11:35:06AM -0500, David Sugar wrote:
> This I want to look at more closely.  My first concern is that it does not 
> break mingw32 cross-compiles.  I think I will have a chance to look at this 
> over the weekend.
> 
> David
> 
> On Thursday 27 February 2003 11:24 pm, Makino Takaki wrote:
> > Dear commonc++ developers,
> >
> > I'd like to post a patch to make commonc++2 compilable in a latest
> > Cygwin environment on Windows.  It seems that the commonc++2 package
> > cannot be compiled via configure script on current Cygwin release.
> > I hope that the patch helps development of this excellent library.
> >
> > The following patch is to fix the compilation error for pthread
> > emulation of Cygwin. It would be more efficient if I could make use of
> > native Win32 API, but it seems a lot of patching effort...
> > I confirmed the patch on Cygwin 1.3.19 and commoncpp2 1.0.8.
> >
> > The changes are:
> >  * Remove !defined(__CYGWIN32__) from #if surronding PosixThread class.
> >  * Disabled PosixThread::waitSignal when sigwait() is not available. I'm
> >    not sure why sigwait() is disabled on Cygwin, and I don't know
> >    what workaround is available for it.  Anyway it seems working happily
> >    without PosixThread::waitSignal member function.
> >  * Added some stuff for socklen_t.  Current configure script cannot find
> >    socklen_t in Cygwin; socklen_t is #define'd under cygwin/socket.h,
> >    but configure applies EGREP_HEADER to only sys/socket.h.  Though my
> >    patch for this problem may be too naive...
> >
> > Best regards,




reply via email to

[Prev in Thread] Current Thread [Next in Thread]