[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ruby18, -pthreads, deep recursion
- To: freebsd-ports_(_at_)_freebsd_(_dot_)_org
- Subject: Re: ruby18, -pthreads, deep recursion
- From: lemon <lemon+freebsd_(_at_)_zomo_(_dot_)_co_(_dot_)_uk>
- Date: Tue, 06 Nov 2007 07:42:50 +0000
- Cc: mwisnicki+freebsd_(_at_)_gmail_(_dot_)_com
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.
_______________________________________________
freebsd-ports_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org