[gentoo-user] sys-libs/glibc-2.15-r1

Stefan G. Weichinger

unread,

Apr 22, 2012, 2:00:01 PM4/22/12

to

Just browsed the changelog of glibc-2.15:

http://sourceware.org/ml/libc-alpha/2012-03/msg00836.html

When I read the NEWS section there with all that "optimized" stuff I
wonder if it makes any sense to rebuild packages here after upgrading glibc?

Stefan

Volker Armin Hemmann

unread,

Apr 22, 2012, 2:10:01 PM4/22/12

to

no, because it is a library. You make use of it anyway.

--
#163933

Stefan G. Weichinger

unread,

Apr 22, 2012, 2:20:02 PM4/22/12

to

Am 22.04.2012 20:05, schrieb Volker Armin Hemmann:

> no, because it is a library. You make use of it anyway.

Ah, yes, sure ... thanks for the explanation.

Nikos Chantziaras

unread,

Apr 22, 2012, 2:30:02 PM4/22/12

to

I think you're a bit confused about how shared libraries work. The
major reason for their existence is that when you update a shared
library, everything that was linked against it will use the updated
version. So if you installd glibc-2.15, all packages will now use that
version instead of 2.14.

Stefan G. Weichinger

unread,

Apr 22, 2012, 2:50:01 PM4/22/12

to

Am 22.04.2012 20:18, schrieb Nikos Chantziaras:

> I think you're a bit confused about how shared libraries work. The
> major reason for their existence is that when you update a shared
> library, everything that was linked against it will use the updated
> version. So if you installd glibc-2.15, all packages will now use that
> version instead of 2.14.

Yes, you and Volker are right, I wasn't fully aware of that fact.
Thanks, Stefan

Pandu Poluan

unread,

Apr 22, 2012, 10:20:02 PM4/22/12

to

What about statically linked packages?

Rgds,

kwk...@hkbn.net

unread,

Apr 22, 2012, 11:30:02 PM4/22/12

to

Bless those who keeps on telling people there is no need to rebuild
packages after glibc upgrade, for they must have not used pam or any
other packages that uses dlopen().

Kerwin.

signature.asc

Graham Murray

unread,

Apr 23, 2012, 1:40:01 AM4/23/12

to

kwk...@hkbn.net writes:

> Bless those who keeps on telling people there is no need to rebuild
> packages after glibc upgrade, for they must have not used pam or any
> other packages that uses dlopen().

So which packages need to be rebuilt? Owing to the initial
non-availability of the patch file, glibc was the last package I built
before rebooting. So far I have seen no problems. I can log in as both
user and root, su works, X and KDE are running OK.

glibc is normally very good at maintaining backward compatibility, using
versioned symbols.

Volker Armin Hemmann

unread,

Apr 23, 2012, 8:50:01 AM4/23/12

to

Rebuilt everything. Congrats

Am 23.04.2012 04:17 schrieb "Pandu Poluan" <pa...@poluan.info>:

On Apr 23, 2012 1:09 AM, "Volker Armin Hemmann" <volke...@googlemail.com> wrote:
>

> Am Sonntag,...

Volker Armin Hemmann

unread,

Apr 23, 2012, 8:50:02 AM4/23/12

to

Strange, never had problems in that regard.

Am 23.04.2012 05:24 schrieb <kwk...@hkbn.net>:

On Mon, 23 Apr 2012 09:12:48 +0700
Pandu Poluan <pa...@poluan.info> wrote:

> On Apr 23, 2012 1:09 A...

Florian Philipp

unread,

Apr 23, 2012, 9:10:01 AM4/23/12

to

Am 23.04.2012 04:12, schrieb Pandu Poluan:
>
> On Apr 23, 2012 1:09 AM, "Volker Armin Hemmann"

Are there actually packages out there that do this? Maybe busybox with
USE="static"?

BTW: Another reason for rebuilding (not in this case, but just to be
complete) can be updates in template libraries like dev-libs/boost. Of
course, this cannot happen for things written in plain C, unless we
consider sys-kernel/linux-headers and friends, for example.

Regards,
Florian Philipp

signature.asc

kwk...@hkbn.net

unread,

Apr 23, 2012, 9:20:02 AM4/23/12

to

On Mon, 23 Apr 2012 14:42:28 +0200

Volker Armin Hemmann <volke...@googlemail.com> wrote:

> Strange, never had problems in that regard.

See, for example, the problem described in thread

http://archives.gentoo.org/gentoo-user/msg_264b8690e0ab67e3f55c0967cba101ec.xml

from this list last November with glibc-2.14 upgrade, which I also
encountered when upgrading my stable amd64. Maybe glibc-2.15 has
improved, but I certainly won't risk it when the time comes. I'd
rather spend (waste?) time to buy that peace of mind, rather than
being locked out of my box.

Kerwin.

signature.asc

Volker Armin Hemmann

unread,

Apr 23, 2012, 12:00:01 PM4/23/12

to

Am Montag, 23. April 2012, 06:31:31 schrieb Graham Murray:
> kwk...@hkbn.net writes:
> > Bless those who keeps on telling people there is no need to rebuild
> > packages after glibc upgrade, for they must have not used pam or any
> > other packages that uses dlopen().
>
> So which packages need to be rebuilt?

none?

if you see segfaults everywhere, rebuild. If apps fail to start, think about
rebuilding. But until then, why waste the electricity?

> Owing to the initial
> non-availability of the patch file, glibc was the last package I built
> before rebooting. So far I have seen no problems. I can log in as both
> user and root, su works, X and KDE are running OK.
>
> glibc is normally very good at maintaining backward compatibility, using
> versioned symbols.

--
#163933

Alan McKinnon

unread,

Apr 24, 2012, 6:40:01 AM4/24/12

to

To be fair, a complete rebuild of everything is a relatively huge
task and usually a waste if done routinely.

glibc is never downgraded in any sane system, only upgraded.
The glibc ABI and API hardly ever take anything away, just add new
stuff. Imagine if glibc behaved like boost wrt API changes <shudder>

So leaving everything else intact after upgrading linux-headers and/or
glibc gives a system that tends to do exactly what it did before and is
in no way broken. Sure, one can rebuild all of world at one's leisure
to take advantage of any new features those packages give, but it is
not *required*

This latest pam nonsense is a very rare event. I really don't feel like
doing massive rebuilds routinely to maybe catch rare events...

--
Alan McKinnnon
alan.m...@gmail.com