public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?
Date: Sat, 23 Sep 2006 10:40:34 -0700	[thread overview]
Message-ID: <5bdc1c8b0609231040s5c9a5cd5t24891ca920c80ac9@mail.gmail.com> (raw)
In-Reply-To: <200609231049.43294.prh@gotadsl.co.uk>

On 9/23/06, Peter Humphrey <prh@gotadsl.co.uk> wrote:
> On Saturday 23 September 2006 10:03, Mark Knecht wrote:
>
> > So you did essentially the
> >
> > emerge -e system
> > emerge -e system
> > emerge -e world
> >
> > steps that you did when upgrading gcc to get there?
>
> Er, the GCC upgrade guide [1] only mentions a single emerge -e system to go
> from 3.4.4 to 4.1.1, and that's what I'm doing just now. I hope I don't
> need the second step.
>
> 1.      http://www.gentoo.org/doc/en/gcc-upgrading.xml
>
> --
> Rgds
> Peter

Peter,
   I take it back. I was thinking of something else. Here is the set
of instructions I asked about on this list and was told were correct:

# emerge -uav gcc
# gcc-config i686-pc-linux-gnu-4.1.1
# source /etc/profile
# fix_libtool_files.sh 3.4.6
# emerge --oneshot -av libtool
# emerge -eav system
# emerge -eav world

I actually asked whether the emerge -eav world was necessary or
whether the system was usable after the emerge system was complete.
Boyd said that some folks had had problems so I did the emerge -eav
world and didn't use the system until it was complete.

NOTE: emerge --resume --skipfirst was my friend as a number of
packages didn't build the first time. I picked them up later.

Sorry for the confusion. I shouldn't work from memory! ;-)

Cheers,
Mark

Cheers,
Mark
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-09-23 17:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 19:35 [gentoo-amd64] SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone? Mark Knecht
2006-09-22 23:42 ` [gentoo-amd64] " Duncan
2006-09-23  0:08   ` Mark Knecht
2006-09-23  8:28     ` Christoph Mende
2006-09-23  9:55     ` Greg Bur
2006-09-23 10:03       ` Mark Knecht
2006-09-23 10:16         ` Greg Bur
2006-09-23 10:49         ` Peter Humphrey
2006-09-23 17:40           ` Mark Knecht [this message]
2006-09-23 21:00       ` Duncan
2006-09-25 20:25     ` Sergio Polini
2006-09-25 20:55       ` Piotr Pruszczak
2006-10-08 18:44         ` Sergio Polini
2006-10-08 18:47           ` Peter Davoust
2006-09-26  1:09       ` Mark Knecht

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=5bdc1c8b0609231040s5c9a5cd5t24891ca920c80ac9@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-amd64@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