cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test sigsuspend_d.c src/lib/libpthread/thread thr_cancel.c thr_concurrency.c thr_create.c thr_find_thread.c thr_init.c thr_kern.c thr_nanosleep.c thr_private.h thr_sig.c thr_sigmask.c ...

[David Xu]

----- Original Message ----- 
From: "Julian Elischer" <julian at elischer.org>
To: "Poul-Henning Kamp" <phk at phk.freebsd.dk>
Cc: "David Xu" <davidxu at FreeBSD.org>; <obrien at FreeBSD.org>; <src-committers at FreeBSD.org>; <cvs-src at FreeBSD.org>; <cvs-all at FreeBSD.org>
Sent: Friday, July 18, 2003 3:17 PM
Subject: Re: cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test sigsuspend_d.c src/lib/libpthread/thread thr_cancel.c thr_concurrency.c thr_create.c thr_find_thread.c thr_init.c thr_kern.c thr_nanosleep.c thr_private.h thr_sig.c thr_sigmask.c ... 


> 
> 
> On Fri, 18 Jul 2003, Poul-Henning Kamp wrote:
> 
> > In message <007101c34cdb$5b2fbd70$f001a8c0 at davidw2k>, "David Xu" writes:
> > >
> > >----- Original Message ----- 
> > >From: "David O'Brien" <obrien at FreeBSD.org>
> > >To: "Julian Elischer" <julian at elischer.org>
> > >Cc: "David Xu" <davidxu at FreeBSD.org>; <src-committers at FreeBSD.org>; <cvs-src at FreeBSD.org>; <cvs-all at FreeBSD.org>
> > >Sent: Friday, July 18, 2003 9:03 AM
> > >Subject: Re: cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test sigsuspend_d.c src/lib/libpthread/thread thr_cancel.c thr_concurrency.c thr_create.c thr_find_thread.c thr_init.c thr_kern.c thr_nanosleep.c thr_private.h thr_sig.c thr_sigmask.c ...
> > >
> > >
> > >> On Thu, Jul 17, 2003 at 04:15:19PM -0700, Julian Elischer wrote:
> > >> > We'll probably make a libpthread-1:1.so and a libpthread-m:n.so.
> > >> 
> > >> I like the names -- makes it very clear what is going on.
> > >
> > >It is better to not use ':' in name, AFAIK,
> > >':' is a shell PATH separator, we'd avoid this.
> > 
> > Seconded, we have had problems with : in filenames before, mostly
> > Makefile problems.
> 
> It wasn't a specific name but a "meta name"
> The names Dan has been thinking of are libthread and libpthread
> but I think there could be some name pair that is more expressive
> of what is going on than that..
> 
> alernatively one library that acts in two different ways..
> 

Think about static library (we still support it), you still
need to compile it twice. so having two libraries is a good
idea. Dynamic changing threading mode at initial time
only works for shared library. :-)

David Xu