public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc and gcc updated to 2.3.5
Date: Thu, 18 Aug 2005 01:40:14 +0200	[thread overview]
Message-ID: <4303CADE.4090907@planet.nl> (raw)
In-Reply-To: <49bf44f105081716301bee29fa@mail.gmail.com>

Grant schreef:
>>>I noticed my glibc and gcc were updated to 2.3.5 in my last big emerge
>>>world.  Should I run an emptytree emerge now?
>>>
>>>- Grant
>>
>>first, your gcc got not updated to 2.3.5
>>
>>second: no.
>>You do NOT NEED to do an emptytree. Never!
>>
>>glibc updates are nothing to worry about, one replaces the other, the software
>>does not care much. And if it cares, it crashes, so you'll see it, if
>>anything needs to rebuild.
>>
>>But as a general rule: you do not need to do an emerge emptytree.
> 
> 
> I remember reading about a package update after which it is beneficial
> to emerge emptytree.  I thought it was the compiler stuff.  Am I
> remembering that wrong?
> 

You're probably not remembering completely. The only time it is
*suggested* that you might want to do an emerge -e world is after you
have recompiled glibc to use NPTL. And even then, plenty of people will
tell you it's not necessary.

Certainly it's not necessary for a normal update of glibc, much less
gcc. Everything will pretty much update itself as you update the
programs, and it's otherwise not an issue.

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-17 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 22:31 [gentoo-user] glibc and gcc updated to 2.3.5 Grant
2005-08-17 23:01 ` Volker Armin Hemmann
2005-08-17 23:30   ` Grant
2005-08-17 23:40     ` Holly Bostick [this message]
2005-08-18  1:03       ` Grant

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=4303CADE.4090907@planet.nl \
    --to=motub@planet.nl \
    --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