| 1 |
On Mon, 23 Apr 2012 09:12:48 +0700 |
| 2 |
Pandu Poluan <pandu@××××××.info> wrote: |
| 3 |
|
| 4 |
> On Apr 23, 2012 1:09 AM, "Volker Armin Hemmann" |
| 5 |
> <volkerarmin@××××××××××.com> wrote: |
| 6 |
> > |
| 7 |
> > Am Sonntag, 22. April 2012, 19:52:16 schrieb Stefan G. Weichinger: |
| 8 |
> > > Just browsed the changelog of glibc-2.15: |
| 9 |
> > > |
| 10 |
> > > http://sourceware.org/ml/libc-alpha/2012-03/msg00836.html |
| 11 |
> > > |
| 12 |
> > > When I read the NEWS section there with all that "optimized" |
| 13 |
> > > stuff I wonder if it makes any sense to rebuild packages here |
| 14 |
> > > after upgrading |
| 15 |
> glibc? |
| 16 |
> > > |
| 17 |
> > |
| 18 |
> > no, because it is a library. You make use of it anyway. |
| 19 |
> > |
| 20 |
> |
| 21 |
> What about statically linked packages? |
| 22 |
> |
| 23 |
> Rgds, |
| 24 |
|
| 25 |
Bless those who keeps on telling people there is no need to rebuild |
| 26 |
packages after glibc upgrade, for they must have not used pam or any |
| 27 |
other packages that uses dlopen(). |
| 28 |
|
| 29 |
Kerwin. |
Archives