I still had ImageMagick 6. Then rmagick didn't work anymore becuase imagemagick was updated. So, if you are having this issue try: rvm reinstall --disable-binary 2. You must have ImageMagick 6. While prepping a development server earlier this afternoon I ran into an issue installing the rmagick gem. You may need configuration options.
I follow this link suggestion to run rvm install 2. To check if your version of ruby is set up correctly, you can use the following. You may need configuration options. . I fully explain the installation process in. Leave a comment if this doesn't get you sorted.
For whoever runs into this problem in the future: It took me long but it's fixed. I'm running a debian server and upgraded all packages after quite a while apt-get update, apt-get upgrade, apt-get distro-upgrade. I tried installing Compass and it failed on the native binaries with a recent clean install of Ubuntu. Might still be safer to manually link the specific libraries than a brew link --force though. In that case, just repeat the procedure.
Done Building dependency tree Reading state information. I ran the following command in terminal, but it couldn't find the libmagick9-dev libary. I am on Snowleopard 10. The original copy of ImageMagick that I installed from source is still on the machine, but I don't know where exactly or how to remove it. This could take a while. I finally got it working by utilizing a script for ImageMagick installation on github.
Have a question about this project? You may need configuration options. You may need configuration options. But if anyhow possible I would prefer to use a later version. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Got same error for alpine 3.
This could take a while. Additional copyrights and licenses apply to this software. When both Magick-config and pkg-config exist, Magick-config is used. This was one of a list of 30 or so gems required by a Ruby project that was being installed onto the development server. It seems that there are some path that are not correctly handled when using the --with-prefix option. I thought initially something else was wrong because I had run into this issue before but I thought I had installed ImageMagick via the yum package manager to resolve the problem.
You may need configuration options. Do you want to continue? Well, the compiler invocations are all happening through the gem command you force the compiler to look in alternate locations with the -I flag, but this user is not using the compiler directly and its best to set things up with the configure command such that goodness occurs without having to alter anything else. From now on, if you run a command that needs to reference ImageMagick, you can prefix it with that command. Magick-config is not found anywhere on your system. Rvm is just a tool to help you manage your rubies. Updating and is a painful expierence.
Any plans on supporting ImageMagick 7? This could take a while. Do you have apt installed on your machine? So I ended up installing an older version of ImageMagic. Last release of this project dated Aug 2016. You may need configuration options. I don't have time to test right now. The below example output is from the mkmf.
This could take a while. This means your native binaries are compiled on your machine. Responses to similar questions recommended installing ImageMagick, which I successfully did. You may need configuration options. This could take a while. You must have ImageMagick 6.
And if it can not be installed, the whole application can not be started. Make sure you have the necessary development packages installed. So this updation is causing the problem in some gem installation like here. Thanks again for taking the time to respond. You may need configuration options. Otherwise manual symlinking of libMagickWand etc is necessary.