From: Roy Wright <royw@cisco.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc-4.1.1
Date: Wed, 07 Jun 2006 14:27:57 -0500 [thread overview]
Message-ID: <448728BD.8040908@cisco.com> (raw)
In-Reply-To: <342e1090606071109o302d8573rce7d2b4d6b2ce3b6@mail.gmail.com>
Daniel da Veiga wrote:
> I'm watching this topic with curiosity, I have switched to ~x86
> recently and after it all (and a few debugging) I have all my packages
> testing now, but have not switched to the new GCC for fear of things
> breaking beyound my knowledge on how to fix it. So, if people start
> replying saying things are stable with the new GCC I might switch to
> it completely and wait a few days before the "emerge -e system &&
> emerge -e world" completes.
>
I was running stable with a lot of testing unmasked. Then upgraded
to gcc-4.1.1 with an immediate emerge -s && emerge -e, which went
mostly smooth.
Then decided to go ~x86 for the system. That is where the pain was,
particularly expat which caused most of kde/gnome to need to be
upgraded. Unfortunately a lot of the tools to do the rebuild also
depended on expat. So it was update a few packages, rebuild a tool,
update a few more packages, ... Lesson learned is when upgrading
to expat-2, immediately take the hours needed to do the
revdep-rebuild (in all honesty, I didn't see the ewarn message
because I was upgrading 448 packages). It really would have been
nice if the expat-2 emerge package died after giving the instructions
to revdep-rebuild...
So far (5 days) the system has been real nice, no problems. KDE
appears (subjective) faster (with USE=kdehiddenvisibility). So +1 on
upgrading a ~x86 to gcc-4.1.1.
For those considering stable to testing, the main changes are
pam-logon/shadow (unmerge pam-logon), coldplug/udev (unmerge
coldplug), expat (revdep-rebuild), ocaml (dependent packages must
be manually rebuilt afterwards).
HTH,
Roy
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-07 19:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ad4496950606070647s5a4bc702m8deeda7dbd590c4a@mail.gmail.com>
2006-06-07 13:53 ` [gentoo-user] gcc-4.1.1 Mohammed Hagag
2006-06-07 14:30 ` Peper
2006-06-07 14:35 ` Julien Cabillot
2006-06-07 14:45 ` Kristian Poul Herkild
2006-06-07 14:56 ` Neil Bothwick
2006-06-07 15:00 ` Bo Ørsted Andresen
2006-06-07 15:25 ` Conneries wearegeeks
2006-06-07 16:04 ` Roy Wright
2006-06-07 17:46 ` Mike Huber
2006-06-07 18:09 ` Daniel da Veiga
2006-06-07 19:27 ` Roy Wright [this message]
2006-06-07 19:55 ` Daniel da Veiga
2006-06-07 18:17 ` Evan Klitzke
2006-06-07 23:25 ` Richard Fish
2006-06-08 0:32 ` Evan Klitzke
2006-06-08 4:40 ` Richard Fish
2006-06-08 11:39 ` Mohammed Hagag
2006-06-08 1:50 ` Bob Young
2006-06-08 2:10 ` Jerry McBride
2006-06-12 21:35 ` Bob Young
2006-06-13 0:09 ` Richard Fish
2006-06-08 4:24 ` Richard Fish
2006-06-08 12:34 ` Bob Young
2006-06-08 13:31 ` Hans-Werner Hilse
2006-06-08 14:00 ` Bob Young
2006-06-08 14:28 ` Bo Ørsted Andresen
2006-06-08 14:57 ` Bob Young
2006-06-08 15:27 ` Toby Cubitt
2006-06-08 18:05 ` Richard Fish
2006-06-09 11:50 ` Vladimir G. Ivanovic
2006-06-09 19:43 ` Richard Fish
2006-06-16 17:25 ` Thomas T. Veldhouse
2006-06-16 17:50 ` Bob Young
2006-06-16 17:17 ` Thomas T. Veldhouse
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=448728BD.8040908@cisco.com \
--to=royw@cisco.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