Date: Sat, 22 Mar 1997 17:33:43 +1100 (EST) From: John Birrell <jb@cimlogic.com.au> To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Cc: freebsd-hackers@freebsd.org Subject: Re: libc_r Message-ID: <199703220633.RAA15734@freebsd1.cimlogic.com.au> In-Reply-To: <199703220501.VAA12058@paris.CS.Berkeley.EDU> from Josh MacDonald at "Mar 21, 97 09:01:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Josh MacDonald wrote: > Hi, I read the pthread(3) man page and it says I need to build > libc_r myself in order to use threads. I could do this, but > its inconvenient. How come it isn't being distributed in the > binary distributions? In current, libc_r was left as optional to avoid (a) lengthening the build time when most people probably didn't want it; and (b) breaking a `make world' in the event that there were problems in the libc_r build. The binary distributions (I guess you mean SNAPs) contain what normally gets built. Of course Jordan could read the pthread man page too, and add WANT_LIBC_R to his environment before building a SNAP. ;-) I think there are enough people using libc_r now to enable it permanently in sys/lib/Makefile, leaving an environment variable to turn it off. There are no quirks to the libc_r build -- from time to time edits are made to libc Makefiles without corresponding edits in libc_r Makefiles. I'd like to merge all the Makefiles to avoid this problem, but this adds complexity to the libc Makefiles that people might not want. > > -josh > Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org CIMlogic Pty Ltd, 119 Cecil Street, South Melbourne Vic 3205, Australia Tel +61 3 9690 6900 Fax +61 3 9690 6650 Mob +61 418 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703220633.RAA15734>