Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-user-cs
Navigation:
Lists: gentoo-user-cs: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-user-cs@g.o
From: Andrej Kacian <ticho@g.o>
Subject: Re: ako postupovať pri update glibc
Date: Fri, 9 Feb 2007 10:41:36 +0100
On Fri, 9 Feb 2007 09:59:02 +0100
"Tomas Jankovic" <tomas.jankovic@...> wrote:

> 1. variant - prekompilovať s glibc aj gcc a binutils
> 2. variant - prekompilovať s glibc aj system, plus skompilovať jadro
> 3. variant - prekompilovať s glibc aj system, world a nakoniec jadro

Hm, a co ma jadro spolocne s glibc? Ved sa spusta davno predtym nez je
namounteny akykolvek suborovy system, na ktorom by nejaky glibc mohol
byt.

Podla 2.5 release notes[1] by v 2.5 nemali byt ziadne zmeny v ABI, cize
kompilovat znovu world (system je podmnozina world-u) asi velky zmysel
nema.

No a revdep-rebuild pravdepodobne potrebovat tiez nebudes, kedze vsetko
co sa linkuje proti glibc sa linkuje proti symlinkom, ktore sa nemenia
pre 2.x verzie, cize napr. "libc.so.6":

-rwxr-xr-x 1 root root 1196560 Nov 11 07:12 libc-2.4.so
lrwxrwxrwx 1 root root      11 Nov 11 07:12 libc.so.6 -> libc-2.4.so

Po upgrade na glibc-2.5 bude tento ukazovat na novy libc-2.5.so.


1. http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/NEWS?rev=1.147.2.21&content-type=text/x-cvsweb-markup&cvsroot=glibc

-- 
Andrej

--
gentoo-user-cs@g.o mailing list


References:
ako postupovať pri update glibc
-- Tomas Jankovic
Navigation:
Lists: gentoo-user-cs: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: ako postupovať pri update glibc
Next by thread:
maskovane USE
Previous by date:
Re: ako postupovať pri update glibc
Next by date:
maskovane USE


Updated Jun 17, 2009

Summary: Archive of the gentoo-user-cs mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.