[gentoo-user] glibc and gcc updated to 2.3.5

[gentoo-user] glibc and gcc updated to 2.3.5

[Grant]

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

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] glibc and gcc updated to 2.3.5

[Volker Armin Hemmann]

On Thursday 18 August 2005 00:31, Grant wrote:
> 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. 
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] glibc and gcc updated to 2.3.5

[Grant]

> > 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?

- Grant

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] glibc and gcc updated to 2.3.5

[Holly Bostick]

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

Re: [gentoo-user] glibc and gcc updated to 2.3.5

[Grant]

> > 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

Ok, thanks Holly.

- Grant

-- 
gentoo-user@gentoo.org mailing list