Date: Thu, 29 Aug 2002 12:26:20 -0400 (EDT) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Michael Lucas <mwlucas@blackhelicopters.org> Cc: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: Porting libc_r from -current to -stable Message-ID: <Pine.GSO.4.10.10208291221420.7188-100000@pcnet1.pcnet.com> In-Reply-To: <20020829100913.A22334@blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Aug 2002, Michael Lucas wrote: > On Thu, Aug 29, 2002 at 03:03:19PM +0100, Jonathon McKitrick wrote: > > On Thu, Aug 29, 2002 at 09:45:49AM -0400, Daniel Eischen wrote: > > | You're going to have to keep the hashtable method of locking > > | FILEs. > > > > So is this project much more complicated than simply resolving symbols and > > dropping unused calls? > > Absolutely. Fasten your seat belt, you're in for a ride. > > Of course, if you pull it off, you will win copious accolades. :-) Actually, it's not all that bad. Jonathon just got hung up in one area that is relatively easy to fix (-stable libc_r already contains the ability to lock FILEs). When you are porting it, try to make it easy to keep the two versions in sync. Feel free to change -current's libc_r to accomodate this (i.e., use macros or something for __sys_XXX so that you can easily switch between _thread_sys_XXX and __sys_XXX). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10208291221420.7188-100000>