Date: Tue, 06 Nov 2007 07:42:50 +0000 From: lemon <lemon+freebsd@zomo.co.uk> To: freebsd-ports@freebsd.org Cc: mwisnicki+freebsd@gmail.com Subject: Re: ruby18, -pthreads, deep recursion Message-ID: <47301AFA.4050902@zomo.co.uk> In-Reply-To: <fgfjnj$ump$1@ger.gmane.org> References: <472A3F63.9010500@zomo.co.uk> <200711012202.42025.josh@tcbug.org> <fgfjnj$ump$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcin Wisnicki wrote: > On Thu, 01 Nov 2007 22:02:38 -0500, Josh Paetzel wrote: >> On Thursday 01 November 2007 04:04:35 pm lemon wrote: >>> [0] http://lists.freebsd.org/pipermail/freebsd-ports/2005- > January/019352.html >>> http://lists.freebsd.org/pipermail/freebsd-ports/2006- > March/030691.html >> If it's any consolation, I've emailed the ruby maintainer a few times >> about why disabling threads in the port's menu doesn't *really* disable >> threads and have never gotten a reply. > > As explained in abovementioned links, some of ruby extensions need > pthreads but since shared modules on freebsd are never linked with > threading libraries (i think it might no longer be true in releng7/ > current), you have no other choice than to link ruby interpreter binary > with libpthread. Thanks, that's much clearer for me now. I guess I'm lucky - I've yet to hit anything involved in our RoR app that breaks a pthread-less ruby18 on 6.2-R. Even better if the problem's gone away on 7.x. Cheers for all the responses. Regards, l.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47301AFA.4050902>