Re: include: Define sigset_t in pthread.h if HAVE_SIGSET_T isn't defined.

[Paul Vriens]

Rob Shearman wrote:
> ---
>  include/wine/pthread.h |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
>
> ------------------------------------------------------------------------

Hi Rob,

MingW has it's own definition of sigset_t (include/sys/types.h) which conflicts 
with this.

Do we need to guard the definition in pthread.h with a "!defined(__MINGW32__)" 
or is this something that needs to be fixed on the MingW side.

(Maybe change our configure?)

-- 
Cheers,

Paul.

include: Define sigset_t in pthread.h if HAVE_SIGSET_T isn't defined.

[Rob Shearman]

2008/9/10 Paul Vriens <paul.vriens.wine(a)gmail.com>:
> Rob Shearman wrote:
> > ---
> >  include/wine/pthread.h |    5 +++++
> >  1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > ------------------------------------------------------------------------
>
> Hi Rob,
>
> MingW has it's own definition of sigset_t (include/sys/types.h) which
> conflicts with this.
>
> Do we need to guard the definition in pthread.h with a
> "!defined(__MINGW32__)" or is this something that needs to be fixed on the
> MingW side.
>
> (Maybe change our configure?)

Yes, configure should detect it. If it doesn't then it's a bug in our
configure check.

-- 
Rob Shearman

include: Define sigset_t in pthread.h if HAVE_SIGSET_T isn't defined.

[Paul Vriens]

Rob Shearman wrote:
> 2008/9/10 Paul Vriens <paul.vriens.wine(a)gmail.com>:
> > Rob Shearman wrote:
> > > ---
> > >  include/wine/pthread.h |    5 +++++
> > >  1 files changed, 5 insertions(+), 0 deletions(-)
> > >
> > > ------------------------------------------------------------------------
> >
> > Hi Rob,
> >
> > MingW has it's own definition of sigset_t (include/sys/types.h) which
> > conflicts with this.
> >
> > Do we need to guard the definition in pthread.h with a
> > "!defined(__MINGW32__)" or is this something that needs to be fixed on the
> > MingW side.
> >
> > (Maybe change our configure?)
>
> Yes, configure should detect it. If it doesn't then it's a bug in our
> configure check.

Hi Rob,

AJ put in a fix for this.

-- 
Cheers,

Paul.