Re: glibc release management

[Thorsten Kukuk <kukuk at suse dot de>]

Hi,

On Fri, Jan 14, Geoff Keating wrote:

> > Date: Fri, 14 Jan 2000 09:45:41 +0100
> > From: Thorsten Kukuk <kukuk@suse.de>
> 
> > With glibc 2.1.3 the current situation is more worse. Not from
> > binary compatiblity, but there are far to much patches which breaks
> > to many other plattforms.
> 
> I looked at the ChangeLog between 2.1.2 and 2.1.3, just to check this.
> 
> There were something like 300 changes (which would sort of confirm
> previous comments about how we need to make maintenance releases more
> often...) but I only saw two (excluding Hurd patches) which I thought
> would be too extensive to be suitable for such a release in general,
> because of the likelihood they would cause problems.  One was the
> change to setrlimit(), the other was the powerpc ld.so changes (which
> I put in myself).

I don't speak about such big changes. I speak about all the little
changes which break other platforms. Ever tried to compile the
current glibc 2.1.3 cvs snapshot on PowerPC or Sparc without
patches ? Or use the current version on Intel ?
Today the libc only works on Alpha without problems and patches.
Sparc (fix from Jakub exists) and PowerPC doesn't compile, mmap
on Intel seg.faults (you need the glibc 2.2 fix).

  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/       kukuk@suse.de
SuSE GmbH            Schanzaeckerstr. 10            90443 Nuernberg
Linux is like a Vorlon.  It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.