1 |
Pandu Poluan wrote: |
2 |
> On Wed, Aug 10, 2011 at 08:14, Dale<rdalek1967@×××××.com> wrote: |
3 |
> |
4 |
>> Pandu Poluan wrote: |
5 |
>> |
6 |
>>> I noticed Dale's email (hi Dale!) [1] asking about which gcc / glibc |
7 |
>>> unstable to use. |
8 |
>>> |
9 |
>>> Is there any consensus yet as to which 'gcc'? I'm planning on doing an |
10 |
>>> `emerge -e @system` on two fresh installs, one x86 and the other |
11 |
>>> amd64. |
12 |
>>> |
13 |
>>> Should I go with 4.5.3? Or 4.5.2? Or play it safe and use 4.5.1-r1 |
14 |
>>> (which, based on b.g.o search [2], seems to have less (serious) bugs |
15 |
>>> compared to 4.5.2) |
16 |
>>> |
17 |
>>> |
18 |
>> Howdy, |
19 |
>> |
20 |
>> I'm using this: |
21 |
>> |
22 |
>> root@fireball / # equery list gcc glibc |
23 |
>> * Searching for gcc ... |
24 |
>> [IP-] [ ] sys-devel/gcc-4.4.5:4.4 |
25 |
>> [IP-] [ ] sys-devel/gcc-4.5.3:4.5 |
26 |
>> |
27 |
>> |
28 |
> So, 4.5.3 is quite safe for day-to-day usage eh? |
29 |
> |
30 |
> Okay, keywording it. Thanks! |
31 |
> |
32 |
> |
33 |
>> * Searching for glibc ... |
34 |
>> [IP-] [ ] sys-libs/glibc-2.13-r4:2.2 |
35 |
>> root@fireball / # |
36 |
>> |
37 |
>> The higher gcc is the one in use. Everything compiles fine. One thing tho, |
38 |
>> I started a download and went to town. When I got back, I was sitting at my |
39 |
>> grub menu. Most likely not related but wanted to mention juuuuuuuuust in |
40 |
>> case. ;-) Yea, my reboot issues is happening again. :-@ |
41 |
>> |
42 |
>> |
43 |
> Hmmm, just a hunch: Have you tried updating the motherboard's firmware? |
44 |
> |
45 |
> Rgds, |
46 |
> |
47 |
|
48 |
I did upgrade it a while back. I'll check and see if there is a new one |
49 |
now. I hadn't thought of that before. We all know that a update fixes |
50 |
some bugs but introduces several new ones. lol Reminds me of Raid. |
51 |
Kill some but new babies come out a few days later. New bugs but still |
52 |
problems. :/ |
53 |
|
54 |
Thanks much. Great hunch. |
55 |
|
56 |
Dale |
57 |
|
58 |
:-) :-) |