ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory

Added by George Plymale at 2011-07-28 06:06 pm

I'm seeing the following failure on a local install for development of ChiliProject on Mac OS X and was hopeful for some insights as to why this may be occuring:
https://github.com/rmagick/rmagick/issues/31


Replies (6)

RE: rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory - Added by Craig Price at 2011-07-28 07:20 pm

No idea either, but I had the same problem and ended up telling bundle to ignore rmagick. Supposedly it is optional.

Of course, that only got me one step further... damn thing still won't run, as I've chronicled in another post these last few days. I'm kind of interested if you end up with the same problem.

RE: rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory - Added by Tiago Franco at 2011-07-28 08:25 pm

The best way to install RMagick on Mac is using Homebrew http://mxcl.github.com/homebrew/. Give it a try if you're having issues.

Thanks

RE: rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory - Added by George Plymale at 2011-07-28 08:31 pm

Hey Tiago, thanks for the note. Unfortunately I did have issues with that a month ago and today regarding ImageMagick via `brew install imagemagick`. (see: https://github.com/mxcl/homebrew/issues/6683 ) The bottom line was that I got it compiling by way of a hack that shouldn't really be necessary... but yes, ImageMagick isn't the issue at play here, it's really rmagick. I do not see any options to `brew install rmagick`... Am I missing something?

I would, indeed, like to keep rmagick installed through rvm if possible, but sure, I'd be happy if it worked the other way as well for the moment.

-George

RE: rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory - Added by Tiago Franco at 2011-07-28 08:49 pm

No, you're not. I confused the two libraries. :|

Ok, from the error it seems an header file is missing. Can you run the "indetify" command on the shell?

Thanks,
TF

RE: rmagick 1.15.17 Compliation Failure on Mac OS X: error: intern.h: No such file or directory - Added by George Plymale at 2011-07-29 04:35 pm

Okay... After quite a haul I managed to get `bundle install` to work. For rmagick, I ended up pushing the ruby version back to ruby-1.8.7-p352 on rvm. Could not get it to run without a core dump initially, however I was able to install it by forcing a gcc as I'm on Lion which uses llvm for compilation by default:
`CC=/usr/bin/gcc-4.2 rvm install ruby-1.8.7 --force`

After this I needed to update my gem version by just redownloading setup from rubygems.org. I then was able to run `gem bundle install` and found that `bundle install` failed once again due to missing ghostscript. Homebrew failed for me, so I moved back to MacPorts which worked like a charm for `port install ghostscript`. Seems that perhaps Homebrew is not yet mature enough from experiences I've had so far.

Finally `bundle install` worked fine:
Fetching source index for http://rubygems.org/
Using rake (0.9.2)
Using activesupport (2.3.12)
Using rack (1.1.2)
Using actionpack (2.3.12)
Using actionmailer (2.3.12)
Using activerecord (2.3.12)
Using activeresource (2.3.12)
Using coderay (0.9.8)
Using edavis10-object_daddy (0.4.3)
Using i18n (0.4.2)
Using mocha (0.9.12)
Using rails (2.3.12)
Using rdoc (3.8)
Installing rmagick (1.15.17) with native extensions
Installing ruby-openid (2.1.8)
Installing rubytree (0.5.3)
Installing shoulda (2.10.3)
Installing sqlite3-ruby (1.2.5) with native extensions
Using bundler (1.0.15)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.

Yes, I did remove mysql from the Gemfile as well as postgresql. I don't reall need those personally at the moment.

I am getting some strange ruby crashes sporadicly on Mac OS X though it seems and I'm note yet able to hunt those down. I think it has to do with perhaps the GCC vs LLVM issue perhaps. I have a bug report submitted to Apple on this one.

-George

(1-6/6)