From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gcc error compiling imagemagic
Date: Wed, 24 Jun 2009 12:23:00 -0500 [thread overview]
Message-ID: <87ab3x8s23.fsf@newsguy.com> (raw)
emerging imagemagick ... I hit this gcc error:
[...]
-L/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/work/ImageMagick-6.5.2-9/PerlMagick/../magick/.libs -lMagickCore -L/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/work/ImageMagick-6.5.2-9/PerlMagick/../wand/.libs -lMagickWand -lperl -lm \
***
gcc-config: error: could not run/locate 'i486-pc-linux-gnu-gcc'
***
make[3]: *** [blib/arch/auto/Image/Magick/Magick.so] Error 1
make[3]: Leaving directory `/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/work/ImageMagick-6.5.2-9/PerlMagick'
make[2]: *** [install-exec-perl] Error 2
make[2]: Leaving directory `/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/work/ImageMagick-6.5.2-9'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/work/ImageMagick-6.5.2-9'
make: *** [install] Error 2
Between the asterisks ... it appears to be looking for the wrong gcc.
Setting from /etc/make.conf
## from an old backup ##
CFLAGS="-O2 -march=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
I did once have 486 in there but followed the gcc guide to get changed
up.
That guide recommended removing the old 486 files... in a couple of
places but I don't recall they were in a bin directory.
I do see some i486 files in /usr/bin:
i486-pc-linux-gnu-c++ i486-pc-linux-gnu-g++
i486-pc-linux-gnu-cpp i486-pc-linux-gnu-gcc
i486-pc-linux-gnu-gfortran
but also the i686 are there too:
i686-pc-linux-gnu-addr2line i686-pc-linux-gnu-g++
i686-pc-linux-gnu-ar i686-pc-linux-gnu-g++-4.3.2
i686-pc-linux-gnu-as i686-pc-linux-gnu-gcc
i686-pc-linux-gnu-c++ i686-pc-linux-gnu-gcc-4.3.2
i686-pc-linux-gnu-c++-4.3.2 i686-pc-linux-gnu-gfortran
i686-pc-linux-gnu-c++filt i686-pc-linux-gnu-gfortran-4.3.2
i686-pc-linux-gnu-cpp i686-pc-linux-gnu-gprof
i686-pc-linux-gnu-cpp-4.3.2 i686-pc-linux-gnu-ld
i686-pc-linux-gnu-nm
i686-pc-linux-gnu-objcopy
i686-pc-linux-gnu-objdump
i686-pc-linux-gnu-ranlib
i686-pc-linux-gnu-readelf
i686-pc-linux-gnu-size
i686-pc-linux-gnu-strings
i686-pc-linux-gnu-strip
Is this the source of the trouble... looks like all the i486 are also there
as i686 too...
And the build environment recorder at:
/var/tmp/portage/media-gfx/imagemagick-6.5.2.9/temp/environment
appears to show nothing but i686..
ARCH=x86
ARCH_LIB=/usr/lib/perl5/5.8.8/i486-linux
CBUILD=i686-pc-linux-gnu
CDEFINE_default=__unix__
CFLAGS='-O2 -march=i686 -pipe'
CFLAGS_default=
CHOST=i686-pc-linux-gnu
CHOST_default=i686-pc-linux-gnu
CROSSCOMPILE_OPTS=
CTARGET_default=i686-pc-linux-gnu
CVSROOT=/usr/local/cvsroot
CVS_RSH=ssh
CXXFLAGS='-O2 -march=i686 -pipe'
DEFAULT_ABI=default
DEFINED_PHASES=' compile configure install prepare setup test unpack'
Also I tried something may have not been all to bright.
I renamed the i486 files listed above... trying to see it that made a
difference, but imagemagick build process is still looking for an
i486 file:
From most recent emerge attempt:
[...]
make[3]: i486-pc-linux-gnu-gcc: Command not found
[...]
Anyone know what is causing this?
next reply other threads:[~2009-06-24 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:23 Harry Putnam [this message]
2009-06-24 18:23 ` [gentoo-user] Re: gcc error compiling imagemagic Harry Putnam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ab3x8s23.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox