From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: SOLVED: [gentoo-user] emerge -eav system failed building sandbox
Date: Sat, 9 Sep 2006 18:06:06 -0700 [thread overview]
Message-ID: <5bdc1c8b0609091806n2c868d3j4b2c732ff0dc4ccf@mail.gmail.com> (raw)
On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
<SNIP>
> However there is a lot of stuff hanging around right now:
>
> lightning ~ # ls -la /usr/bin/*gcc*
> -rwxr-xr-x 1 root root 11536 Sep 9 12:07 /usr/bin/gcc
> lrwxrwxrwx 1 root root 62 Jun 20 18:05 /usr/bin/gcc-3.4.6 ->
> /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.6/x86_64-pc-linux-gnu-gcc
> lrwxrwxrwx 1 root root 62 Sep 9 12:07 /usr/bin/gcc-4.1.1 ->
> /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/x86_64-pc-linux-gnu-gcc
> -rwxr-xr-x 1 root root 18567 Sep 9 10:45 /usr/bin/gcc-config
> -rwxr-xr-x 1 root root 11536 Sep 9 12:08 /usr/bin/gcc32
> -rwxr-xr-x 1 root root 11536 Sep 9 12:08 /usr/bin/gcc64
> -rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/gccbug
> -rwxr-xr-x 1 root root 2050 Sep 9 14:59 /usr/bin/gccmakedep
> -rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/i686-pc-linux-gnu-gcc
> -rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/i686-pc-linux-gnu-gccbug
> -rwxr-xr-x 1 root root 11536 Sep 9 12:07 /usr/bin/x86_64-pc-linux-gnu-gcc
> lrwxrwxrwx 1 root root 62 Jun 20 18:05
> /usr/bin/x86_64-pc-linux-gnu-gcc-3.4.6 ->
> /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.6/x86_64-pc-linux-gnu-gcc
> lrwxrwxrwx 1 root root 62 Sep 9 12:07
> /usr/bin/x86_64-pc-linux-gnu-gcc-4.1.1 ->
> /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/x86_64-pc-linux-gnu-gcc
> -rwxr-xr-x 1 root root 11536 Sep 9 12:08 /usr/bin/x86_64-pc-linux-gnu-gcc32
> -rwxr-xr-x 1 root root 11536 Sep 9 12:08 /usr/bin/x86_64-pc-linux-gnu-gcc64
> -rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/x86_64-pc-linux-gnu-gccbug
> lightning ~ #
>
> It seems that others may have fixed this by erasing the
> /usr/bin/i686-pc-* files.
>
> - Mark
>
Richard,
I moved the i686-gcc files to a remote directory. With that change
sandbox now emerges cleanly:
>>> Original instance of package unmerged safely.
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/sandbox-1.2.17 merged.
>>> Recording sys-apps/sandbox in "world" favorites file...
>>> No packages selected for removal by clean.
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* Regenerating GNU info directory index...
* Processed 153 info files.
* IMPORTANT: 4 config files in /etc need updating.
* Type emerge --help config to learn how to update config files.
lightning ~ #
I will now retry the emerge -eav world and see if I can get through
the whole process cleanly.
Cheers,
Mark
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2006-09-10 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5bdc1c8b0609091806n2c868d3j4b2c732ff0dc4ccf@mail.gmail.com \
--to=markknecht@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