Date: Fri, 20 Jan 2006 09:08:58 +0900 From: UEDA Hiroyuki <bsdmad@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: Ruby 1.8.4 and Rails problems Message-ID: <4cb05bee0601191608r1937e25cr@mail.gmail.com> In-Reply-To: <c6bf2550601191030g6c149551u9968296e288db207@mail.gmail.com> References: <c6bf2550601190815l606a92d1x11e4388238eb48fd@mail.gmail.com> <43CFD2AD.2070501@innerewut.de> <c6bf2550601191007u1c8fa993xe4144a5c5d8fefea@mail.gmail.com> <43CFD91A.8070604@innerewut.de> <c6bf2550601191030g6c149551u9968296e288db207@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2006/1/20, James Earl <james@icionline.ca>: ; > It was actually this latest update that seemed to break things for me. > I was running Ruby 1.8.4 around the beginning of the week without any > problems. It was just after I updated another server running Rails > apps yesturday that I started having problems. I then updated my > desktop computer's Ruby port today to see if it would also break my > Rails apps, and it did. I have heard some application which doesn't use mod_ruby also dumps core with latest ruby ports. The ruby was enabled pthreads and after disabling pthreads with "--WITHOUT_PTHREADS=3Dyes", the application have worked well. So maybe your problem will be solved by rebuilding ruby with "--WITHOUT_PTHREADS=3Dyes". -- UEDA "BSD mad" Hiroyuki <bsdmad@gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4cb05bee0601191608r1937e25cr>