apr_sigwait/SunOS compile break

[Cliff Woolley <jc...@cs.virginia.edu>]

Just a heads up on something I ran across a day or so ago in case you all
get a chance to look at it before you roll again (I probably won't have a
chance to look at it before then).

I'm still having problems with an incorrectly detected number of arguments
to sigwait on SunOS as of Friday, I think, and AFAIK no patches have gone
in to fix it.  I know this was mentioned on the list earlier this week...
were any conclusions reached?  Basically, it's a problem of SunOS having
different numbers of arguments for sigwait depending upon what is
#defined... I seem to recall it was a problem with the configure script
not including all the right CFLAGS.

Just wanted to bring it back up in case a new tarball is being rolled
again soon, in case there's a chance it can get fixed before then.  If the
next tarball is going to be a few days off, I'll look into it myself.

--Cliff

Re: apr_sigwait/SunOS compile break

[Jeff Trawick <tr...@bellsouth.net>]

Cliff Woolley <jc...@cs.virginia.edu> writes:

> I'm still having problems with an incorrectly detected number of arguments
> to sigwait on SunOS as of Friday, I think, and AFAIK no patches have gone
> in to fix it.  I know this was mentioned on the list earlier this week...
> were any conclusions reached?  Basically, it's a problem of SunOS having
> different numbers of arguments for sigwait depending upon what is
> #defined... I seem to recall it was a problem with the configure script
> not including all the right CFLAGS.

When we tested sigwait() we didn't have some thread-related flags
turned on yet.  But those thread-related flags get us a different
flavor of sigwait() later.

I'm not sure a conclusion on how to handle was reached either.  I'll
just make up one.

-- 
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...

Re: apr_sigwait/SunOS compile break

[Jeff Trawick <tr...@bellsouth.net>]

Cliff Woolley <jc...@cs.virginia.edu> writes:

> I'm still having problems with an incorrectly detected number of arguments
> to sigwait on SunOS as of Friday, I think, and AFAIK no patches have gone
> in to fix it.  I know this was mentioned on the list earlier this week...
> were any conclusions reached?  Basically, it's a problem of SunOS having
> different numbers of arguments for sigwait depending upon what is
> #defined... I seem to recall it was a problem with the configure script
> not including all the right CFLAGS.

When we tested sigwait() we didn't have some thread-related flags
turned on yet.  But those thread-related flags get us a different
flavor of sigwait() later.

I'm not sure a conclusion on how to handle was reached either.  I'll
just make up one.

-- 
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...