Re: Compile failure

[Jeff Bailey]

On Wed, Dec 13, 2000 at 12:32:58PM -0500, Alain Magloire wrote:

> You are right, it will clash everywhere I do a
> #ifdef HAVE_PTHREAD_H
> #  define __USE_UNIX98
> #  include <pthread.h>
> #endif

Should the configure test to see is __USE_UNIX98 is ok?

> > I added a flag to configure to handle this.  It seems to send some other 
> > things funny though, so I'll look at that later.  (./configure 
> > --disable-pthread)
> 
> Ok, I see what you're doing.  Actually the default should rather
> be to not compile with Threading support but to allow it when passing
> --with-pthread.  IMO it should be the opposite, but many OSes seem not
> to have a good POSIX threading package.

Do you know of any tradition to follow from other packages?  If we're 
going to require a flag to get all of the functionality, it should be 
the same everywhere.

> I'm suggesting this:
> ./configure --with-pthread
> provide an stub implementation of read_write locks base
> of minimal pthread semantics(condvar and mutex) in mailutils/lib/rwlock.c
> 
> --with-pthread will check for -lpthread, <pthread.h>, etc ... and set
> AC_DEFINE(HAVE_PTHREAD_H)
> AC_DEFINE(WITH_PTHREAD)
> AC_DEFINE(HAVE_PTHREAD_RWLOCK_INIT)
> etc ...
> 
> I see if I can clear this out tonight.

Okay.  If there's something you need, let me know.

> > These errors in the pthread.h start right after:
> > 
> > #ifdef __USE_UNIX98
> > /* Functions for handling read-write locks.  */
> 
> This looks like a bug in the include files<pthread.h>, the idea was to let
> one pick different namespaces(implementations) there was a lot of
> noise in the glibc list about this and that it was a bad thing.

Do you want me to do anything on this?

-- 
No matter how big the bell, if you only tap it, it can give out only a
faint sound.  We must understand thoroughly that the weakness of the blow,
not a fault of the bell makes the sound poor. 
 - Koichi Tohei