From: Benjamin J. <bhj...@gm...> - 2007-12-01 20:52:58
|
Some more information: The warning I'm getting is due to some conditional code which compiles differently if the target is Tiger starting at RBRuntime.m:527. I imagine this wasn't caught before as few people are building for both Tiger and Leopard and also using threads. I tried compiling on Leopard (10.5.0) as suggested by Mr. Kimura in an earlier thread on rubycocoa-devel, and was unable to compile it with the specified flags: ruby install.rb config --macosx-deployment-target=10.4 --build-universal=yes \ --sdkroot=/Developer/SDKs/MacOSX10.4u.sdk When running setup, this configuration gave the following error, both on the head of the trunk and the revision referred to in the thread (r2131). : ld: library not found for -lffi Satoshi Nakagawa was also able to verify this error on 10.5.1 On Dec 1, 2007 1:47 PM, Benjamin Jackson < bhj...@gm...> wrote: > 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 > > > > |