From owner-freebsd-current Fri Nov 22 10:33:25 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 84AF737B401; Fri, 22 Nov 2002 10:33:23 -0800 (PST) Date: Fri, 22 Nov 2002 10:33:23 -0800 From: Juli Mallett To: Robert Watson Cc: walt , freebsd-current@freebsd.org Subject: Re: libpthread question Message-ID: <20021122103323.B32466@FreeBSD.org> References: <3DDE332A.4090104@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@freebsd.org on Fri, Nov 22, 2002 at 09:29:52AM -0500 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Robert Watson [ Data: 2002-11-22 ] [ Subjecte: Re: libpthread question ] > On Fri, 22 Nov 2002, walt wrote: > > > I noticed David Xu's changes to libpthread this morning, so I did a > > "make libraries" and noticed with surprise that libpthread.so.5 was > > still dated Sep 16. > > > > I then did 'cd /usr/src/lib' and a 'make' and noticed that libpthread > > did not show up during the make. > > > > At that point I looked at /usr/src/lib/Makefile and noticed that > > libpthread is not mentioned there at all. > > > > Then I 'cd /usr/src/lib/libpthread' and 'make' and everything recompiled > > in my /usr/src tree, not my /usr/obj tree. > > > > So, am I screwed up somehow, or is this expected behavior? > > This is expected behavior -- libpthread is currently disconnected from the > build. I'd actually like to see it connected to the build, with an > appropriate "WARNING: DRAGONS INCLUDED" man page also hooked up to > discourage accidental use. At least, assuming David Xu, Jon Mini, etc, > are ready for the resulting bug reports they'll get. No. You really don't want to do this. A lot of ports will see -lpthread and try to use it instead of letting gcc use its best judgement about what threads system to use (-pthread). And in the current state, that means a _lot_ of broken stuff. -- Juli Mallett OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message