Date: Wed, 27 Jan 1999 15:33:23 -0600 From: "Richard Seaman, Jr." <dick@tar.com> To: Frikkie Thirion <frix_bsd@hotmail.com> Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: Wine and FreeBSD clone port Message-ID: <19990127153323.L421@tar.com> In-Reply-To: <19990127201154.28449.qmail@hotmail.com>; from Frikkie Thirion on Wed, Jan 27, 1999 at 12:11:54PM -0800 References: <19990127201154.28449.qmail@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 27, 1999 at 12:11:54PM -0800, Frikkie Thirion wrote: > Hi there > > I'm currently running 3.0-RELEASE with my ports and src updated to > present state via CTM. I've rebuild world with the > -DCOMPAT_LINUX_THREADS and -DVM_STACK switches in /etc/make.conf as > described at http://lt.tar.com. At lt.tar.com I alse found a port for > FreeBSD which will emulate the Linux thread/clone function. The port > installed like a charm, and I included therefrom the -D_THREAD_SAFE and > -lpthread (as well as some include and lib paths) switches into my > /etc/make.conf. > The problem that I'm experiencing is that wine still doesn't detect the > clone function during its auto configuration procedure and subsequently > builds without thread support. > > Has anyone had any success with this? Not that I know of (you're the first report of trying to compile wine with the linux threads "port"). Based on what someone told me a while ago, wine doesn't use "pthread" threads, but rather calls "clone" directly. Is this your understanding? If so, there could be a variety of problems, possibly related to how wine tries to detect the existence of "clone". The clone call I added to the linux threads "port" wasn't (or hasn't yet) been designed to do anything other than compile with the "port". If it tries to detect the clone call in the headers, I think linux glibc declares the clone call in the sched.h header. So, possibly if you added the clone declarations from clone.h in the port to your system sched.h headers, they would get detected if thats how the detection goes. Or, if it examines libc to find the clone call (this is where it is in linux glibc), we would maybe have to add the clone call to libc instead of putting it into the linux pthread library. If you can find out how wine goes about detecting the clone call, let me know and I'll try to help some more. -- 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-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990127153323.L421>