From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -uD world dies: "Unable to build"
Date: Tue, 29 Jan 2008 08:15:18 +0000 [thread overview]
Message-ID: <200801290815.48300.michaelkintzios@gmail.com> (raw)
In-Reply-To: <642851.81992.qm@web31709.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On Tuesday 29 January 2008, maxim wexler wrote:
> > Read this guide carefully and follow it to the
> > letter:
> >
> > http://www.gentoo.org/doc/en/gcc-upgrading.xml
>
> deeper and deeper...
>
>
> "It is safe to remove the older GCC version at this
> time. If you feel the need, please issue the following
> command (as usual, substitute =sys-devel/gcc-3.4* with
> the version you want to uninstall):"
>
> gcc-4.1.2 was already emerged earlier but running gcc
> --version reveals 3.4.6, so I ran
>
> #emerge -aC =sys-devel/gcc-3.4.6-r2
>
> <...>
> --- !empty dir /etc/eselect
> --- !empty dir /etc/env.d/gcc
> --- !empty dir /etc/env.d
> --- !empty dir /etc
> * Running 'fix_libtool_files.sh 3.4.6'
> * Scanning libtool files for hardcoded gcc library
> paths...
> gcc-config error: Could not run/locate "gcc"
>
> :0: assertion failed: (gcc -dumpversion) | getline
>
> NEWVER)
Are you sure that you have emerged (successfully) the latest stable gcc?
> And now I don't seem to have any sort of gcc:
>
> localhost heathen # gcc --version
> gcc-config error: Could not run/locate "gcc"
>
> and emerge -uD world still fails at the same place.
Retrace your steps and follow the guide on this one. I'm sure that you can
recover if you ended up with no gcc, but don't know off hand what it takes to
do it. (I am sure that the forums are full of suggestions for this problem).
If you are certain that you have had the correct gcc installed and gcc-config
shows that it has been selected, and you have finished with the steps
suggested in the guide above, then run revdep-rebuild -X -p -v once more for
good measure before you try to emerge anything else.
HTH.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-29 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 22:03 [gentoo-user] emerge -uD world dies: "Unable to build" maxim wexler
2008-01-28 22:25 ` Mick
2008-01-29 0:23 ` maxim wexler
2008-01-29 0:42 ` Neil Bothwick
2008-01-29 1:52 ` maxim wexler
2008-01-29 8:15 ` Mick [this message]
2008-01-29 21:50 ` Alan McKinnon
2008-01-29 22:27 ` [gentoo-user] emerge -uD world dies: "Unable to build" FIXED maxim wexler
2008-01-29 15:13 ` [gentoo-user] Chinese reader needed WAS emerge -uD world dies: "Unable to build" maxim wexler
2008-01-29 15:35 ` Willie Wong
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=200801290815.48300.michaelkintzios@gmail.com \
--to=michaelkintzios@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