From: Benjamin J. <bhj...@gm...> - 2007-12-01 15:47:53
|
Some more information: I just recompiled ruby 1.8.6 out of the box with the patch applied, as well as updating RC to the trunk and recompiling as described in the wiki for running on both Tiger and Leopard. My output after running standaloneify from otool -L: http://pastie.textmate.org/private/3umxwejpjybbwwu2epya Looks to me like everything's linked as it should be. On any leopard machine, the "RBCocoaInstallRubyThreadSchedulerHooks: couldn't find autoreleasePool ivar" error appears and the app is working with a non-patched ruby. Any help or pointers to information would be greatly appreciated. Thanks, Ben On Nov 30, 2007 11:44 AM, Benjamin Jackson <bhj...@gm...> wrote: > Hi all, > > We are embedding RubyCococa and the patched libruby with standaloneify, > and it works out of the box on 95% of the machines, but some of our users > have been getting crashes due to problems with ruby threads: > > "RBCocoaInstallRubyThreadSchedulerHooks: couldn't find autoreleasePool > ivar" > > Also seeing a warning about ruby threads not being able to be used without > patches to the ruby interpreter. > > Can anyone suggest what might be going on here, and if there might be > something specific to the users' setup which is FUBAR-ing RubyCocoa? I'm > certain that I'm linking against my own version of libruby, as the same > program works on Tiger machines out of the box with no changes to the > installed ruby. > > Thanks in advance, > > Ben > |