Re: Why Gnome RPMS need to work with RH 5.2

[James Henstridge <james daa com au>]

glibc2.1 is supposed to be backward compatible.  That is why it has the
same soname as glibc2.0.  Applications that rely on internal symbols of
glibc2.0 (which no applications are supposed to do) may break (the only
one I heard about was staroffice, and they were asked not to use those
symbols).

If you want to make sure that gnome runs on your system, try building from
the source tarballs (or make your own personal RPMs, which is what I do).
This way you don't have to worry about these version problems.

James Henstridge.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Tue, 6 Apr 1999, Eric Wood wrote:

> Hall wrote:
> > If you got your gnome packages from RedHat's Starbuck ftp site, yes, those
> > do require glibc2.1. 
> 
> I've run into the same problem when wanting to upgrade to the latest
> linuxconf.  It too requires glibc2.1.  If I upgrade to glibc2.1, I
> probably can get the latest GNOME and linuxconf packages to work but
> I'll probably break a lot of other stuff.
> 
> I thought that linux could have multiple versions of the same library. 
> Shouldn't glibc2.1 have it own linked files instead of picking on
> libc.so.6 -or- is glibc2.1 fully backward compatible and I'm worried
> over nothing?
> 
> -Eric Wood
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>