ansaurus

Question

Answer 1

A:

It reports that it tried to execute some native code, which was in the right executable format, but for the wrong architecture. This probably means that there is either still a mismatch between the gem version and the running kernel, or that some temporary code which was created when you still had your old operating system installed is still there. Two possible solutions might be:

Make a backup of your application, find the offending ".ruby_inline" directory and delete it, then try again.
Find out where the "RubyInline" and "image_science" gems are installed (e.g. gem list -d image_science) and check that their native parts (usually those within gems//lib or something similar, those in "bin" or those with a ".so" extension) match your kernel. You can use the "file" tool to examine whether a file is a 32 or 64 bit executable (simply call file filename).

cite 2009-09-02 17:32:36

Thank you for the response. I found the /tmp/.ruby_inline/ directory in my app and blew it away, uninstall the RubyInline and image_science gems, and port uninstalled freeimage. Then reinstalled the gems as x86_64 and port reinstalled freeimage (3.12.0_0). I still got the error.What is strange, is even with all of those gems and ports uninstalled, I restarted the server and loaded a page and the same "mach-o" error came up.

Mighty 2009-09-02 18:58:57

Did you investigate the executable (i.e., native) parts of those two gems as I sugested? Did you campre the output to, e.g., the rails binary?

cite 2009-09-02 20:06:07

Sorry, probably a bit of a noob here when it comes to this, but I found where the gems are stored (/usr/local/lib/ruby/gems/1.8) and found the RubyInline and image_science directory and found several files in /lib and /bin, but they are all .rb files, which I assume aren't the executable files. I did the "file" examination of them and the obviously came back as "-w script text executable." I must be missing something...

Mighty 2009-09-02 21:01:58

Ok, I found a little more info. I was able to examine an ImageScience executable file and determine that it is i386, but it wasn't in the gems directory, it was here: /config/initializers/../tmp/.ruby_inline/Inline_ImageScience_cdab.bundle. I blew the whole .ruby_inline/ away, reinstalled everything again and it still doesn't work.

Mighty 2009-09-02 23:18:54

Sorry, still struggling with this...So after port-uninstalling free_image, and gem-uninstalling RubyInline and image_science, I wanted to see what the error would be:[I have to post the error in a separate comment below. Ran out of chars here...]I don't know if there is anything to glean from this, but I did notice references to the i386 arch even BEFORE any of the relevant add-ons were installed. This leads me to believe that there are other gems/ruby infrastructure that aren't running at 64-bit, which may be causing problems.Anyone have any thoughts on this?

Mighty 2009-09-03 12:00:39

ld: library not found for -lfreeimagecollect2: ld returned 1 exit statusProblems loading ImageScienceProcessor: error executing "cc -arch i386 -pipe -bundle -undefined dynamic_lookup -I/opt/local/include -fno-common -arch i386 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common -I /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I

Mighty 2009-09-03 12:02:06

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/include -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -o \"app/config/initializers/../tmp/.ruby_inline/Inline_ImageScience_cdab.bundle\" \"/app/config/tmp/.ruby_inline/Inline_ImageScience_cdab.c\" -L/opt/local/lib -lfreeimage -lfreeimage -lstdc++ ": 256Renamed /app/config/initializers/../tmp/.ruby_inline/Inline_ImageScience_cdab.c to /app/config/initializers/../tmp/.ruby_inline/Inline_ImageScience_cdab.c.bad

Mighty 2009-09-03 12:03:36

Two things strike me as odd: (1) Hte build process for ImageScience explicitely mentioning "i386" instead of "x86_64" and second, the freeimage library not being found.

cite 2009-09-03 18:33:21

Figured it out. I had "i386" in my bash profile. Once I changed it to: "export ARCHFLAGS='-arch x86_64'" it works. Ugh. Thank you so much for your help.

Mighty 2009-09-03 19:50:24

Answer 2

+1 A:

I had the same problem that some gem dependencies (especially the C based ones) needed to be reinstalled for the 64 bit (snow leopard) environment. I used the ruby console for this. Here's what I did:

$ irb
  irb> `gem list`.each_line {|line| `sudo env ARCHFLAGS="-arch x86_64" gem install #{line.split.first}`}

Colins 2009-09-04 07:22:12

Answer 3

A:

After doing what colins peters mentioned above (the code to reinstall 64-bit gems), I also had to change the directory where my IDE is looking for gems. Since RubyMine didn't do it for me, or I didn't find it, I did this:

cd ~/.gem/ruby/1.8/
rm -r gems
ln -s /Library/Ruby/Gems/1.8/gems gems

alex 2009-11-04 22:22:20

ansaurus

tags:

views:

answers:

Snow Leopard / 64-bit ruby gem problem?

related questions