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 O'Brien]

On Thu, Jul 17, 2003 at 07:12:56PM -0400, Daniel Eischen wrote:
> On Thu, 17 Jul 2003, David Xu wrote:
> 
> > davidxu     2003/07/17 16:02:30 PDT
> > 
> >   FreeBSD src repository
> > 
> >   Modified files:
> >     lib/libpthread       Makefile 
> >     lib/libpthread/test  sigsuspend_d.c 
> >     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 
> >                           thr_sigpending.c thr_sigsuspend.c 
> >                           thr_sigwait.c thr_yield.c 
> >   Log:
> >   o Eliminate upcall for PTHREAD_SYSTEM_SCOPE thread, now it
> >     is system bound thread and when it is blocked, no upcall is generated.
> >   
> >   o Add ability to libkse to allow it run in pure 1:1 threading mode,
> >     defining SYSTEM_SCOPE_ONLY in Makefile can turn on this option.
> 
> Anyone know what makefile hackery to use to get a library
> built twice, each time with a different name?  We want
> to build libpthread as M:N and libthread as 1:1, all
> with the same sources, but with SYSTEM_SCOPE_ONLY
> defined for the latter build.  Do we need a different
> directory just for this?

I would create src/lib/libkse/{libpthread,libthread}, and have
src/lib/libkse/Makefile.inc0 that contains everything to build the libs
except for the -D's and the lib name.  Have
src/lib/libkse/{libpthread,libthread}/Makefile include ../Makefile.inc0
and define the missing parts.

The BSD Makefile framework really does depend and expect separate
directories for each product.

-- 
-- David  (obrien at FreeBSD.org)