ImageMagick Won't Emerge [Solved]

palsyboy · Apprentice Joined: 08 Jun 2004 Posts: 262 Location: USA

If I try to install imagemagick, I get the following error:

sonicbhoc · Posted: Sat Nov 18, 2006 7:41 pm Post subject:

That wasn't the error message, I can't figure out what's wrong from that. That's a call stack - the error message is a few lines up. Try compiling it again and post the errors it prints to the terminal.

palsyboy · Apprentice Joined: 08 Jun 2004 Posts: 262 Location: USA

Sorry about that. Here's what it says:

sonicbhoc · Posted: Sat Nov 18, 2006 8:20 pm Post subject:

Can you give me a few more lines? sorry to bother you so much.

palsyboy · Apprentice Joined: 08 Jun 2004 Posts: 262 Location: USA

No need to apologize - you're the one helping me.

I was typing all that manually from my Linux machine to my Mac, since I don't yet have a running X-server. I decided to try getting it running so I could just copy the code over from Konsole to Firefox, but I found out that I was missing some necessary parts of make.conf. I'm now running a major emerge --newuse, so it might be a while before I get back to this thread.

At least I finally pulled my head out of my rear to figure out that ImageMagick is necessary for gimp-print, not the GIMP itself. :oops:

quietScot · n00b Joined: 19 Nov 2006 Posts: 6 Location: Newcastle, UK

Hi,

I've been having the same problem when emerging 'gnome-light' with imagemagick failing.

The only way I could find of fixing it is (being a relative newbie and trying to interpret other posts/internet) was to add a '-perl' flag to package.use for imagemagick . Looking at imagemagick.org there's some threads suggesting the perl element of the implementation might be a bit flaky currently.

Doing this and then emerging, imagemagick complied, but the compiler complained about not being able to find various Xorg libraries during the compile - so I don't think this is an ideal solution.

Any pointers would be appreciated.

buckyball · n00b Joined: 28 Oct 2002 Posts: 14 Location: Fremont, CA

Here's what I get:

-SNIP-
i686-pc-linux-gnu-gcc -L../magick/.libs -lMagick -shared -L/usr/local/lib Magick.o -o blib/arch/auto/Image/Magick/Magick.so \
-L/usr/lib -lfreetype -lz -L/usr/lib -ltiff -lfreetype -ljpeg -lfreetype -lz -lfontconfig -lexpat -lXext -lSM -lICE -lX11 -lXt -lbz2 -lz -lpthread -lm -lpthread \

chmod 755 blib/arch/auto/Image/Magick/Magick.so
Manifying blib/man3/Image::Magick.3pm
make[1]: Leaving directory `/var/tmp/portage/imagemagick-6.3.0.5/work/ImageMagick-6.3.0/PerlMagick'

!!! ERROR: media-gfx/imagemagick-6.3.0.5 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_compile
ebuild.sh, line 937: Called src_compile
imagemagick-6.3.0.5.ebuild, line 86: Called die

!!! compile problem
!!! If you need support, post the topmost build error, and the call stack if relevant.
_________________
Buckyball
If it doesn't fit, force it --
if it breaks, it needed fixing anyway!

firre · n00b Joined: 26 Jul 2004 Posts: 7

blixem · n00b Joined: 17 Nov 2006 Posts: 1

guyr · Apprentice Joined: 17 Aug 2004 Posts: 237

Same problem, same fix. Installing x86 from scratch into a virtual machine. Looking back on the original error, why is the build for ImageMagick trying to include the Magick library? That recursive dependency doesn't seem right.
_________________
Guy Rouillier

togan · Last edited by togan on Thu Nov 23, 2006 8:40 pm; edited 1 time in total

palsyboy · Apprentice Joined: 08 Jun 2004 Posts: 262 Location: USA

That fix worked for me, too. Thanks.

SvenFischer · Veteran Joined: 05 Feb 2003 Posts: 1033 Location: Berlin

On my brand new install:

misterjack · Veteran Joined: 03 Oct 2004 Posts: 1655

millerl · n00b Joined: 26 Jul 2004 Posts: 51 Location: Coeur d'Alene

That worked for me too. Thanks!

I was having the same problem!!

cable_guy · n00b Joined: 08 Jan 2005 Posts: 17 Location: Smithers, BC

I had the same problem. -j1 worked awesome here too.
_________________
What, Windows isn't 64bit yet?

rsborn · Posted: Tue Dec 26, 2006 11:46 pm Post subject: Fixed mine too

This is a brand new install under vmware (not that it matters) and the j1 seemed to take care of it for me as well

thanks,
Rick

NickG · n00b Joined: 07 May 2005 Posts: 7 Location: UK

cable_guy · n00b Joined: 08 Jan 2005 Posts: 17 Location: Smithers, BC

I'm not positive but I have an idea. I believe that makeopts is supposed to control the number of parallel processes to use during the build. I think that one of the processes is trying to build code that is dependant on code that has yet to finish in the other process. I admit it's a bit of a guess but it makes a bit of sense to me.
_________________
What, Windows isn't 64bit yet?

lukmih · n00b Joined: 16 Nov 2005 Posts: 13

I just had this same problem and had to use the:

metatinara · n00b Joined: 02 Nov 2006 Posts: 5 Location: Ohio, USA

Padwarmo · n00b Joined: 24 Jan 2007 Posts: 1 Location: Germany

[quote=cable_guy]I'm not positive but I have an idea. I believe that makeopts is supposed to control the number of parallel processes to use during the build. I think that one of the processes is trying to build code that is dependant on code that has yet to finish in the other process. I admit it's a bit of a guess but it makes a bit of sense to me.[/quote]

Turns out to be just that. Seems like make "forgets" to wait for a dependent compilation and moves on to the next step right away. Usually when my non-emerge builds fail with "-j2" I just run make with no -j option set to overcome that error. After that I could go on with -j2.

If you wanna make sure something compiles over night you should remove the "-j2" option in your make.conf - even though it will take longer at least it will finish

Theron NightStar · n00b Joined: 21 Jan 2007 Posts: 7

Leave it to the ever-so-excellent Gentoo Forums to have a solution to a problem waiting here for me!

kg4ysy · Posted: Fri Feb 02, 2007 2:31 am Post subject:

The -j1 worked for me as well. Thanks for help.

rsa4046 · Posted: Thu Feb 08, 2007 2:51 pm Post subject:

++ !
_________________
I love gentoo, but I am certainly no guru, despite what it says above.