Results 1 to 4 of 4

Thread: ImageMagick 6.2

  1. #1
    Join Date
    Dec 2007
    Posts
    4

    Default ImageMagick 6.2

    I have an application that needs mageMagick 6.2 in order to run properly. BH currently uses 6.0.7. any ideas on how to work arround this issue?????
    please advise
    thanks

  2. #2

    Default

    Any time I need software that Bluehost doesn't have installed, I ssh to my account and compile it from source. After compilation, I install it to a directory I have set aside inside my home directory.

    For most software, this is simply a matter of downloading the tarball (.tar.gz .tgz .tar.bz2 file) which contains the source, extracting it, and then running the configure script followed by make and make install.

    This is more or less the process I used to download build, and install ImageMagick:

    Code:
    $ cd sandbox
    $ wget http://image_magick.veidrodis.com/image_magick/ImageMagick-6.3.2-9.tar.bz2
    $ tar jxvf ImageMagick-6.3.2-9.tar.bz2
    $ cd ImageMagick-6.3.2-9
    $ ./configure --prefix=$HOME/local
    $ make && make install
    The --prefix=$HOME/local tells the configure script to build ImageMagick in a way to be installed in your ~/local folder instead of to the system directory.

    I actually ran into two problems while compiling ImageMagick on my account. I got an error about not being able to use the libx11.so provided by the system. Since I'm not going to be using any kind of gui on this server, I changed my configure script to the following:

    Code:
    ./configure --without-x --prefix=$HOME/local
    I then ran into a second problem where the PerlMagick component would not compile. If I don't need Perl support it's sometimes easier to simply disable it:

    Code:
    ./configure --without-x --without-perl --prefix=$HOME/local
    If make gives you an error, and you need to start over, you don't need to redownload or reuncompress the tarball again. You simply need to run your new configure script and then make && make install again.

    Once installed, you'll need to make a change to your .bashrc so that your command line will look towards your own local directory to run commands.

    This is what I have at the bottom of my ~/.bashrc file:

    Code:
    export PATH=$HOME/local/usr/bin:$HOME/local/bin:$PATH
    If you need to make libraries or other language bindings available, you'll need to follow instructions for whatever language you are doing it for.

    You indicated that you needed ImageMagick 6.2. These instructions are for the latest version of ImageMagick. You should either be just as good with the latest version, or you may follow these same instructions (more or less) with the specific version you need.

  3. #3
    Join Date
    Oct 2008
    Posts
    13

    Default

    I ran into this same problem a month ago. I installed a script that required Imagemagic to be upgraded. (Version Bluehost is running is over 4 years old!)

    I contacted support who told me I could not do the update nor would they upgrade it.

    Kind of left a bad taste for Bluehost after that. Fortunately the script vendor modded the application to work with my host.

  4. #4
    Join Date
    Sep 2006
    Posts
    2

    Default

    Bluehost is actively upgrading their servers to CentOS 5.3, from CentOS 4.7. As a result, the version of ImageMagick is in fact being upgraded to 6.2.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •