public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ~amd64 - my experience so far...
Date: Mon, 12 Apr 2010 14:03:30 -0700	[thread overview]
Message-ID: <u2t5bdc1c8b1004121403z49ab463fgb6a5bc0bd4d31df2@mail.gmail.com> (raw)
In-Reply-To: <p2o58965d8a1004121157td93a068esbb5e2ccd0a926e03@mail.gmail.com>

On Mon, Apr 12, 2010 at 11:57 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, Apr 12, 2010 at 1:44 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> Checking if your kit is complete...
>> Looks good
>> MakeMaker FATAL: prerequisites not found.
>>    ExtUtils::Depends not installed
>
> If part of your transition was upgrading from perl 5.8 to 5.10 you
> need to run perl-cleaner like the ewarn says in the perl ebuild. If
> you didn't do that yet then maybe that's the cause.
>
> /usr/sbin/perl-cleaner --all
>

OK, it appears that this was part of the issue. Don't know how I
missed the warning other than there were a number of things and it
must have been in there somewhere. This allowed me to do  emerge -C
kde xfce4-meta and get old stuff off. Now emerge -DuN @world is clean
with 390 packages currently installed. I cleaned everything out of my
user directory just to ensure that any problems aren't caused by old
config files. First step behind me.

Now, at this point I started looking at emerging xfce4-meta again, it
failed with messages about rebuilding xorg-server. When I attempted
that I got error messages about invalid gcc profiles which led me to
discover this problem:

cruncher ~ # gcc-config -l
 * gcc-config: Active gcc profile is invalid!

 [1] x86_64-pc-linux-gnu-4.4.3
cruncher ~ # gcc-config 1
 * Switching native-compiler to x86_64-pc-linux-gnu-4.4.3 ...
 * gcc-config: Active gcc profile is invalid!

 * Your gcc has a bug with GCC_SPECS.
 * Please re-emerge gcc.
 * http://bugs.gentoo.org/68395

>>> Regenerating /etc/ld.so.cache...                                                           [ ok ]

 * If you intend to use the gcc from the new profile in an already
 * running shell, please remember to do:

 *   # source /etc/profile

cruncher ~ #

The bug report suggested the above idea but I couldn't set the profile
to '1' so I did emerge -1 gcc. Hey, at least it lets me watch 12
processor cores max out at 100%. ;-)

5 minutes later....

cruncher ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-4.4.3 *
cruncher ~ #

Now the profile is set and emerge -DuN xfce4-meta was clean. Progress,
I think, but when I try to log in I get logged out automatically with
a message to look at the .xession-errors file:

cruncher mark # cat .xsession-errors
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Cannot find Xclients
/etc/X11/gdm/Xsession: line 203: exec: xterm: not found
cruncher mark #

cruncher mark # eix -I xterm
No matches found.
cruncher mark # updatedb
cruncher mark # slocate xterm | grep bin
cruncher mark #

Unmet dependencies?

Because I'm paranoid about gcc problems and I need to run some errands
I'm going to send this now and start an emerge -e @world. That should
finish up in about 90 minutes I think (I'll time it for fun) and I'll
try again after that.

Thanks,
Mark



  parent reply	other threads:[~2010-04-12 21:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 11:57 [gentoo-user] ~amd64 - my experience so far Mark Knecht
2010-04-12 12:00 ` Alan McKinnon
2010-04-12 12:29   ` Mark Knecht
2010-04-12 12:42     ` William Kenworthy
2010-04-12 12:56       ` Mark Knecht
2010-04-12 13:10       ` [gentoo-user] " Kerin Millar
2010-04-12 12:57     ` [gentoo-user] " Alan McKinnon
2010-04-12 16:33       ` KH
2010-04-13  7:09         ` Alan McKinnon
2010-04-13  7:30           ` William Kenworthy
2010-04-13 12:40             ` Mark Knecht
2010-04-13 15:12               ` Paul Hartman
2010-04-13 16:11                 ` Mark Knecht
2010-04-13 17:34                   ` Alex Schuster
2010-04-13 18:30                     ` Mark Knecht
2010-04-13 15:37               ` Paul Hartman
2010-04-12 14:01     ` Neil Bothwick
2010-04-12 12:14 ` Zeerak Mustafa Waseem
2010-04-12 12:35   ` Mark Knecht
2010-04-12 13:07     ` [gentoo-user] " walt
2010-04-12 18:44       ` Mark Knecht
2010-04-12 18:57         ` Paul Hartman
2010-04-12 19:02           ` Paul Hartman
2010-04-12 21:03           ` Mark Knecht [this message]
2010-04-12 21:14             ` Paul Hartman
2010-04-12 22:18               ` Mark Knecht
2010-04-12 19:02         ` Alex Schuster
2010-04-12 13:06 ` Kerin Millar
2010-04-12 15:45 ` [gentoo-user] " Paul Hartman
2010-04-12 18:30   ` Paul Hartman

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=u2t5bdc1c8b1004121403z49ab463fgb6a5bc0bd4d31df2@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