Date: Tue, 05 Jun 2012 21:14:06 -0400 From: Steve Wills <swills@FreeBSD.org> To: Stanislav Sedov <stas@FreeBSD.org> Cc: FreeBSD Ports <ports@FreeBSD.org>, ruby@FreeBSD.org Subject: Re: Ruby 1.9 as default Message-ID: <4FCEAEDE.8060707@FreeBSD.org> In-Reply-To: <20120605110002.589f1071.stas@FreeBSD.org> 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> <def1973e5aaac34b7e3977ddc1427a6f.squirrel@mouf.net> <20120605110002.589f1071.stas@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
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, Stevehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCEAEDE.8060707>
