From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can not compile / emerge
Date: Tue, 9 Sep 2014 12:45:42 -0600 [thread overview]
Message-ID: <20140909184542.GE23438@syscon7> (raw)
In-Reply-To: <20140909183638.GD23438@syscon7>
On 09/09/14 12:36, Joseph wrote:
>I was installing an application gimp and all of a sudden I got an error:
>
>>>> Emerging (7 of 8) media-gfx/gimp-2.8.10-r1
> * gimp-2.8.10.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [
>ok ]
> * gimp-2.8.10-freetype251.patch SHA256 SHA512 WHIRLPOOL size ;-) ... [
>ok ]
>>>> cfg-update-1.8.2-r1: Creating checksum index...
>>>> Unpacking source...
>>>> Unpacking gimp-2.8.10.tar.bz2 to /var/tmp/portage/media-gfx/gimp-2.8.10-r1/work
>>>> Unpacking gimp-2.8.10-freetype251.patch to /var/tmp/portage/media-gfx/gimp-2.8.10-r1/work
>unpack gimp-2.8.10-freetype251.patch: file format not recognized. Ignoring.
>>>> Source unpacked in /var/tmp/portage/media-gfx/gimp-2.8.10-r1/work
>>>> Preparing source in /var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10 ...
> * Applying gimp-2.7.4-no-deprecation.patch ... [
>ok ]
> * Applying gimp-2.8.10-freetype251.patch ... [
>ok ]
> * Applying gimp-2.8.10-clang.patch ... [
>ok ]
> * Running eautoreconf in '/var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10' ...
> * Running glib-gettextize --copy --force ... [
>ok ]
> * Running intltoolize --automake --copy --force ... [
>ok ]
> * Skipping 'gtkdocize --copy' due gtkdocize not installed
> * Running libtoolize --install --copy --force --automake ... [
>ok ]
> * Running aclocal -I m4macros ... [
>ok ]
> * Running autoconf ... [
>ok ]
> * Running autoheader ... [
>ok ]
> * Running automake --add-missing --copy --force-missing ... [
>ok ]
> * Running elibtoolize in: gimp-2.8.10/
> * Applying portage/1.2.0 patch ...
> * Applying sed/1.5.6 patch ...
> * Applying as-needed/2.4.2 patch ...
> * Applying target-nm/2.4.2 patch ...
> * Fixing OMF Makefiles ... [
>ok ]
> * Disabling deprecation warnings ... [
>ok ]
>>>> Source prepared.
>>>> Configuring source in /var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10 ...
> * econf: updating gimp-2.8.10/config.sub with /usr/share/gnuconfig/config.sub
> * econf: updating gimp-2.8.10/config.guess with /usr/share/gnuconfig/config.guess
>./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
>--sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --docdir=/usr/share/doc/gimp-2.8.10-r1
>--disable-maintainer-mode --disable-gtk-doc --enable-default-binary --disable-silent-rules --with-x --without-aa --with-alsa --disable-altivec --with-bzip2
>--without-libcurl --with-dbus --without-gvfs --without-webkit --with-libjpeg --without-libjasper --with-libexif --with-lcms=lcms2 --without-gs --enable-mmx
>--with-libmng --with-poppler --with-libpng --disable-python --disable-mp --enable-sse --with-librsvg --with-libtiff --with-gudev --without-wmf --with-xmc
>--without-libxpm --without-xvfb-run
>checking for a BSD-compatible install... /usr/bin/install -c
>checking whether build environment is sane... yes
>checking for a thread-safe mkdir -p... /bin/mkdir -p
>checking for gawk... gawk
>checking whether make sets $(MAKE)... yes
>checking whether make supports nested variables... yes
>checking whether make supports nested variables... (cached) yes
>checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
>checking whether the C compiler works... no
>configure: error: in `/var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10':
>configure: error: C compiler cannot create executables
>See `config.log' for more details
>
>
>Now, emerge / equery will not even show up on a command line.
>Most of the time I'm getting an error:
>error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
>
>Running on my other system I get:
>equery b libstdc++.so.6
> * Searching for libstdc++.so.6 ...
>sys-devel/gcc-4.5.4 (/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 -> libstdc++.so.6.0.14)
>
>env-update - doesn't work either
>
>--
>Joseph
I've tried to bootstrap the system and re-install "gcc" but I can not even do "env-update" after running: chroot /mnt/gentoo /bin/bash
--
Joseph
next prev parent reply other threads:[~2014-09-09 18:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 18:36 [gentoo-user] can not compile / emerge Joseph
2014-09-09 18:45 ` Joseph [this message]
2014-09-09 18:46 ` Todd Goodman
2014-09-09 19:02 ` Joseph
2014-09-09 19:15 ` Joseph
2014-09-09 21:38 ` Mick
2014-09-09 21:57 ` Joseph
2014-09-09 22:20 ` Neil Bothwick
2014-09-09 22:49 ` Joseph
2014-09-10 3:29 ` Kerin Millar
2014-09-09 18:49 ` Dale
2014-09-10 2:59 ` Kerin Millar
2014-09-10 3:21 ` Joseph
2014-09-10 3:27 ` Kerin Millar
2014-09-10 3:50 ` [gentoo-user] [SOLVED] " Joseph
2014-09-10 3:57 ` Kerin Millar
2014-09-10 4:16 ` Joseph
2014-09-10 5:01 ` Kerin Millar
2014-09-10 5:10 ` Kerin Millar
2014-09-10 5:32 ` [gentoo-user] BACKUPS Joseph
2014-09-10 7:14 ` Alan McKinnon
2014-09-10 7:47 ` Dale
2014-09-10 7:51 ` J. Roeleveld
2014-09-10 8:03 ` Dale
2014-09-10 9:13 ` Alan McKinnon
2014-09-10 8:34 ` Neil Bothwick
2014-09-10 11:03 ` Kerin Millar
2014-09-10 5:20 ` [gentoo-user] [SOLVED] can not compile / emerge Joseph
2014-09-11 12:07 ` [gentoo-user] " James
2014-09-11 12:28 ` Joseph
2014-09-11 13:36 ` J. Roeleveld
2014-09-12 17:09 ` Joseph
2014-09-11 13:40 ` James
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=20140909184542.GE23438@syscon7 \
--to=syscon780@gmail.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