From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QrD2o-0007Vb-00 for garchives@archives.gentoo.org; Wed, 10 Aug 2011 17:58:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C894521C1F8; Wed, 10 Aug 2011 17:58:08 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 9335321C1EF for ; Wed, 10 Aug 2011 17:57:19 +0000 (UTC) Received: by ywb5 with SMTP id 5so876744ywb.40 for ; Wed, 10 Aug 2011 10:57:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=3ersyrZfOJgk/9sAjMmnIjHmaq3WtXL67c+lNlI+iC4=; b=J0F+UJvrIo2XMlpjZfn13q+C5fJZ2us3ljuGRaw9WAbNYGS0ZusjlSkK7TohwRXmG5 +FiuxMG3Fp9aeSuLZrsMslVe1HF3dcx/cbFUvvMmVh80zHlCeEV2IlM/rnuR5dbkKWmE oPuvXXMR07BddltObJEMtHjLl2Tg2thComUbg= Received: by 10.150.160.7 with SMTP id i7mr9035660ybe.402.1312999039060; Wed, 10 Aug 2011 10:57:19 -0700 (PDT) Received: from [192.168.2.5] (adsl-74-240-55-112.jan.bellsouth.net [74.240.55.112]) by mx.google.com with ESMTPS id y18sm703962ybn.6.2011.08.10.10.57.17 (version=SSLv3 cipher=OTHER); Wed, 10 Aug 2011 10:57:17 -0700 (PDT) Message-ID: <4E42C67B.1050909@gmail.com> Date: Wed, 10 Aug 2011 12:57:15 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110708 Gentoo/2.0.14-r1 SeaMonkey/2.0.14 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Which gcc unstable? References: <4E41DB8C.3010007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: fdbfc3fa22bd76a4c272916788281e54 Pandu Poluan wrote: > On Wed, Aug 10, 2011 at 08:14, Dale 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 :-) :-)