Date: Mon, 21 Dec 1998 12:01:16 -0600 From: Richard Seaman <dick@tar.com> To: Kenneth Wayne Culver <culverk@wam.umd.edu>, Alfred Perlstein <bright@hotjobs.com> Cc: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>, Joseph Lee <nugundam@best.com>, freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r Message-ID: <19981221120116.B5500@tar.com> In-Reply-To: <Pine.GSO.3.95q.981221120220.19175D-100000@rac6.wam.umd.edu>; from Kenneth Wayne Culver on Mon, Dec 21, 1998 at 12:03:55PM -0500 References: <Pine.BSF.4.05.9812211024340.6331-100000@bright.fx.genx.net> <Pine.GSO.3.95q.981221120220.19175D-100000@rac6.wam.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 21, 1998 at 12:03:55PM -0500, Kenneth Wayne Culver wrote: > One thing though, in order for WINE to work with threads, you must get > glibc. It won't work otherwise any differently than it will for FreeBSD. > Also, the linux emulation must be updated to support USER_LDT's. It appears that glibc is already included in the linux emulation if you install the latest linux_lib port. However, it isn't fully identified as such (its just libc.so.6). It appears to work ok with linux threads based on preliminary testing (assuming you are using the very latest 3.0 with COMPAT_LINUX_THREADS enabled). As far as using the Linux threads "port", it doesn't need glibc to run threads. Is there something about Wine that is specfic to glibc? However, linking the Linux threads "port" with the FreeBSD libc will not get you a 100% thread safe solution, yet, as there are some libc functions that are not thread safe yet, and there is no implementation of cancellation points, yet. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981221120116.B5500>