From owner-freebsd-ruby@FreeBSD.ORG Wed Jun 6 01:14:07 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 981A4106566B; Wed, 6 Jun 2012 01:14:07 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b2]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2E38FC12; Wed, 6 Jun 2012 01:14:07 +0000 (UTC) Received: from meatwad.mouf.net (cpe-024-162-230-236.nc.res.rr.com [24.162.230.236]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id q561E6BU068290 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 5 Jun 2012 21:14:06 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4FCEAEDE.8060707@FreeBSD.org> Date: Tue, 05 Jun 2012 21:14:06 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120528 Thunderbird/12.0.1 MIME-Version: 1.0 To: Stanislav Sedov References: <4FC96D45.8080904@FreeBSD.org> <20120601193059.af9201da.stas@FreeBSD.org> <4FCD51E4.4030309@FreeBSD.org> <20120605085202.GI85127@deviant.kiev.zoral.com.ua> <07758721-BD54-4732-9B17-83D4CCCF55E0@freebsd.org> <20120605110002.589f1071.stas@FreeBSD.org> In-Reply-To: <20120605110002.589f1071.stas@FreeBSD.org> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [204.109.58.86]); Tue, 05 Jun 2012 21:14:06 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.97.2 at mouf.net X-Virus-Status: Clean Cc: FreeBSD Ports , ruby@FreeBSD.org Subject: Re: Ruby 1.9 as default X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 01:14:07 -0000 On 06/05/12 14:00, Stanislav Sedov wrote: > You usually cannot dlopen the object linked agains pthread from a > non-pthreaded object. Or it is used to be that way. My understanding is that you can now, IFF your non-threaded object is built with -pthread. > Exec should work > fine, I don't see how this can be an issue. Good point. >> >> Perhaps we need to build ruby with -pthread? >> > > Of course, we already do. Both of them. > Ah, right, I realized this just after I hit send, sorry, need to have my coffee before sending email. :) >From what I saw in your other messages, it sounds like this may be specific to the use of mono. Or can you reproduce with another program? Thanks, Steve