From: Laurent S. <lsa...@ap...> - 2007-11-26 16:37:50
|
This is just a warning and this can be ignored. You can perhaps fix it by removing the modified version of libruby in /usr/lib (normally the installer keeps a backup there of the original version). At a glance it seems that RubyCocoa was built with the stock version of ruby, then you try to use it with a custom version of ruby. Laurent On Nov 26, 2007, at 4:36 PM, Tim Perrett wrote: > Hey Laurent, > > Thanks for the speedy reply. I think its because I have two versions > of ruby installed. Ive managed to get it registering in IRB on my > custom install, but now in IRB I get this message: > > 2007-11-26 15:34:26.220 irb[1999] WARNING: multiple libruby.dylib > found: '/usr/local/lib/libruby.dylib' and '/usr/lib/libruby.1.dylib' > 2007-11-26 15:34:26.220 irb[1999] > RBCocoaInstallRubyThreadSchedulerHooks: warning: > rb_set_cocoa_thread_hooks is linked from a different library (/usr/ > lib/libruby.1.dylib) than ruby_init (/usr/local/lib/libruby.dylib) > > How do I stop it linking to the stock version of ruby? > > Cheers > > Tim > > > > On 26 Nov 2007, at 15:28, Laurent Sansonetti wrote: > >> How did you install? (binary installer, or from the sources?) >> >> On which system did you install on? Do you reproduce the same problem >> on both 10.4 and 10.5? >> >> What happens when you do require 'osx/cocoa'? >> >> What's your Ruby load path? (ruby -e 'p $:'). Verify that the >> RubyCocoa files are there. >> >> Laurent > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |