Pandu Poluan wrote:
On Wed, Aug 10, 2011 at 08:14, Dale<[email protected]> wrote:
Pandu Poluan wrote:
I noticed Dale's email (hi Dale!) [1] asking about which gcc / glibc
unstable to use.
Is there any consensus yet as to which 'gcc'? I'm planning on doing an
`emerge -e @system` on two fresh installs, one x86 and the other
amd64.
Should I go with 4.5.3? Or 4.5.2? Or play it safe and use 4.5.1-r1
(which, based on b.g.o search [2], seems to have less (serious) bugs
compared to 4.5.2)
Howdy,
I'm using this:
root@fireball / # equery list gcc glibc
* Searching for gcc ...
[IP-] [ ] sys-devel/gcc-4.4.5:4.4
[IP-] [ ] sys-devel/gcc-4.5.3:4.5
So, 4.5.3 is quite safe for day-to-day usage eh?
Okay, keywording it. Thanks!
* Searching for glibc ...
[IP-] [ ] sys-libs/glibc-2.13-r4:2.2
root@fireball / #
The higher gcc is the one in use. Everything compiles fine. One thing tho,
I started a download and went to town. When I got back, I was sitting at my
grub menu. Most likely not related but wanted to mention juuuuuuuuust in
case. ;-) Yea, my reboot issues is happening again. :-@
Hmmm, just a hunch: Have you tried updating the motherboard's firmware?
Rgds,
I did upgrade it a while back. I'll check and see if there is a new one
now. I hadn't thought of that before. We all know that a update fixes
some bugs but introduces several new ones. lol Reminds me of Raid.
Kill some but new babies come out a few days later. New bugs but still
problems. :/
Thanks much. Great hunch.
Dale
:-) :-)
