On Mon, May 6, 2013 at 12:28 PM, Chris Cappuccio <[email protected]> wrote:
> Chris Cappuccio [[email protected]] wrote: > > Ted Unangst [[email protected]] wrote: > > > On Fri, May 03, 2013 at 15:46, Jeremy Evans wrote: > > > > > > > > Basically, the native code in the libv8 gem doesn't compile > correctly on > > > > OpenBSD. It probably requires patches (lang/libv8 requires patches > to > > > > compile). There are two ways to go about fixing it: > > > > > > > > 1) Get libv8 to work. You could try installing an updated gcc port > and see > > > > if its g++ will work. If not, you could try building an OpenBSD > port for > > > > the ruby libv8 gem, and either getting it to use the system libv8, or > > > > porting over the lang/libv8 patches so that it builds. > > > > > > >From the libv8 gem readme, it appears you can install it with the > > > system v8 as so: > > > > > > gem install libv8 -- --with-system-v8 > > > > > > And then start all over and hope you can pass go. > > > > That is totally fucking sweet. > > So now that Ruby is up and running... > > I ocassionally get ruby 2.0 to crash on "thin20 start". But not always. > And there appears > to be some looping behavior. Is this showing anything obvious to anyone? > ruby 2.0.0-p0 shipped with some bugs, including ones that can cause crashes. The first ruby 2.0.0 patch release should be coming out sometime this month and should hopefully fix these issues. I'd use ruby 1.9.3 for production in the meantime and try ruby 2.0 again after the next patch release. FWIW, unicorn seems pretty stable with ruby 2.0, so you may want to try it instead of thin if you want to stick with ruby 2.0. Thanks, Jeremy
