public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which gcc unstable?
Date: Wed, 10 Aug 2011 10:22:13 +0700	[thread overview]
Message-ID: <CAA2qdGWXLFWTxb9Xvt-ZbEF+F+MySvBjzDJfnQtb4mEfhxBywA@mail.gmail.com> (raw)
In-Reply-To: <4E41DB8C.3010007@gmail.com>

On Wed, Aug 10, 2011 at 08:14, Dale <rdalek1967@gmail.com> 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,
-- 
Pandu E Poluan
~ IT Optimizer ~

 • Blog : http://pepoluan.tumblr.com
 • Linked-In : http://id.linkedin.com/in/pepoluan



  reply	other threads:[~2011-08-10  3:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  0:55 [gentoo-user] Which gcc unstable? Pandu Poluan
2011-08-10  1:14 ` Dale
2011-08-10  3:22   ` Pandu Poluan [this message]
2011-08-10 17:57     ` Dale
2011-08-10 18:09       ` Dale
2011-08-10 18:48         ` Joost Roeleveld
2011-08-10 19:48           ` Thanasis
2011-08-10 20:38             ` Dale
2011-08-10 21:11               ` pk
2011-08-10 21:48                 ` Dale
2011-08-11  5:56                 ` Joost Roeleveld
2011-08-10 21:47       ` [gentoo-user] " walt
2011-08-10 21:57         ` Dale

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=CAA2qdGWXLFWTxb9Xvt-ZbEF+F+MySvBjzDJfnQtb4mEfhxBywA@mail.gmail.com \
    --to=pandu@poluan.info \
    --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