Date: Tue, 5 Jun 2012 11:00:02 -0700 From: Stanislav Sedov <stas@FreeBSD.org> To: "Steve Wills" <swills@mouf.net> Cc: Stanislav Sedov <stas@freebsd.org>, Konstantin Belousov <kostikbel@gmail.com>, ports@freebsd.org, ruby@freebsd.org, Steve Wills <swills@freebsd.org> Subject: Re: Ruby 1.9 as default Message-ID: <20120605110002.589f1071.stas@FreeBSD.org> In-Reply-To: <def1973e5aaac34b7e3977ddc1427a6f.squirrel@mouf.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Jun 2012 09:43:55 -0400 "Steve Wills" <swills@mouf.net> mentioned: > > > > Is this perhaps the -pthread issue I hit with perl? The issue is that if > you call (dlopen, exec, whatever) a threaded app from a non-threaded on, > it hangs due to the fact that libc takes shortcuts and doesn't initialize > thread related things in non-threaded apps. The solution is to build with > -pthread. (I may be describing the problem wrong, but the solution of > building with -pthread works.) You usually cannot dlopen the object linked agains pthread from a non-pthreaded object. Or it is used to be that way. Exec should work fine, I don't see how this can be an issue. > > Perhaps we need to build ruby with -pthread? > Of course, we already do. Both of them. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120605110002.589f1071.stas>