From: "Michael Crute" <mcrute@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Remerge the system with gcc-4.1?
Date: Fri, 8 Sep 2006 10:33:42 -0400 [thread overview]
Message-ID: <558b73fb0609080733w7374b17dv681cf0a95671f33f@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10609080724m2678c3dbw1f08d6bf265b9ce8@mail.gmail.com>
On 9/8/06, Grant <emailgrant@gmail.com> wrote:
> > I am leaving my office in a moment to put the 2006.1 disk in a server to
> > start a fresh build (it's a standby server and I can afford to have it
> > off line for a day or 2) specifically to avoid having to do the gcc4
> > upgrade. Ive done one so far and it took me 5 days and nearly cost me
> > my laptop -- and I followed the gentoo guide specifically. There has
> > GOT to be a better way. Sadly I cant take each of my servers offline to
> > do upgrade them this way -- some I will have to risk on the GCC upgrade,
> > but for now im avoiding it like the plague.
> >
> > Tim
>
> I've followed the GCC upgrade guide before without problems, but now
> I'm scared. Is all the trouble because of how Gentoo works or how GCC
> works? What is the trouble like? Packages that won't compile, or
> different things breaking in the system?
Methinks there is just a bit of FUD swirling around. I can't speak to
GCC 4.1 (may do it this afternoon) but the last time I did a GCC
upgrade (following the documentation) I had absolutely no problems
whatsoever. If you are really worried tar up your system as a backup
before you start.
-Mike
--
________________________________
Michael E. Crute
http://mike.crute.org
I may not have gone where I intended to go, but I think I have ended
up where I intended to be. --Douglas Adams
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-08 14:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49bf44f10609072007w4c110d77je1152ea578c7e708@mail.gmail.com>
2006-09-08 6:16 ` [gentoo-user] Remerge the system with gcc-4.1? Erik
2006-09-08 6:26 ` Boris Fersing
2006-09-08 7:09 ` jarry
2006-09-08 11:56 ` Timothy A. Holmes
2006-09-08 12:24 ` Dale
2006-09-08 13:11 ` Jean-Marc Beaune
2006-09-08 15:44 ` michael
2006-09-11 15:58 ` Matthias Bethke
2006-09-08 14:24 ` Grant
2006-09-08 14:33 ` Michael Crute [this message]
2006-09-09 0:40 ` Mark Kirkwood
2006-09-08 14:37 ` Andrew Gaydenko
2006-09-08 14:59 ` Neil Bothwick
2006-09-08 15:26 ` Andrew Gaydenko
2006-09-08 16:05 ` Neil Bothwick
2006-09-08 16:18 ` Andrew Gaydenko
2006-09-08 15:12 ` Timothy A. Holmes
2006-09-08 15:30 ` Jean-Marc Beaune
2006-09-08 15:45 ` michael
2006-09-08 17:02 ` Bo Ørsted Andresen
2006-09-08 17:09 ` Timothy A. Holmes
2006-09-08 17:35 ` Bo Ørsted Andresen
2006-09-08 18:07 ` Timothy A. Holmes
2006-09-08 19:05 ` Bo Ørsted Andresen
2006-09-08 19:49 ` Richard Fish
2006-09-08 20:10 ` Timothy A. Holmes
2006-09-08 20:29 ` Richard Fish
2006-09-08 7:22 ` Richard Fish
2006-09-08 21:34 ` [gentoo-user] " Peter
2006-09-08 22:12 ` Richard Fish
2006-09-08 22:20 ` Peter
2007-10-10 5:39 ` Daevid Vincent
2007-10-10 5:51 ` Mark Kirkwood
2007-10-10 22:32 ` Mick
2006-09-08 21:35 ` Peter
2006-09-08 6:23 ` [gentoo-user] " Dirk Heinrichs
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=558b73fb0609080733w7374b17dv681cf0a95671f33f@mail.gmail.com \
--to=mcrute@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