libpthread compile failure

[Ken Gunderson]

On Tue, 28 Mar 2006 15:06:24 -0500
Kris Kennaway <kris at obsecurity.org> wrote:

> On 7.0 during buildworld:
> 
> /usr/src/lib/libpthread/thread/thr_barrier.c:69: error: conflicting types for '_pthread_barrier_init'
> /usr/src/lib/libpthread/../../include/pthread.h:156: error: previous declaration of '_pthread_barrier_init' was here
> /usr/src/lib/libpthread/thread/thr_barrier.c:69: error: conflicting types for '_pthread_barrier_init'
> /usr/src/lib/libpthread/../../include/pthread.h:156: error: previous declaration of '_pthread_barrier_init' was here
> *** Error code 1
> 
> Those two declarations are:
> 
> > int
> > _pthread_barrier_init(pthread_barrier_t *barrier,
> >                       const pthread_barrierattr_t *attr, int count)
> 
> > int             pthread_barrier_init(pthread_barrier_t *,
> >                         const pthread_barrierattr_t *, unsigned);
> 
> What is odd is that I can't see how this suddenly broke.
> 
> Kris
> 

I don't know if in any way related but after a  recent update on
fbsd-5.4- i386 machine I had to start using ruby-nopthreads becuase
previous ROR apps that had been working fine for months were now
borked.  Some ruby gurus helped me track it down to a fbsd pthread
issue and building ruby w/o was the fix.  So apparently a known
issue in ruby crowd.  Kind of confuses portupgrade though...

-- 
Best regards,

Ken Gunderson

Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?