On Thu, Mar 27, 2003 at 11:20:42PM -0600, Doug B wrote:
> If I understand correctly, it seems the reason to jump a major version
> is because the new glibc breaks binary compatability.
>
> OK... that makes sense.
>
> Why then would RedHat introduce a new glibc into RH 8 that breaks
> compatabilty with some programs (wine comes to mind and apparently
> VMWare)? Shouldn't they have patched the glibc version that shipped
> (and worked) rather than break RH 8 with a new version?
Do you know for sure that it breaks things? I'm about to install
it today ...
$ rpm -qp --changelog glibc-2.3.2-4.80.src.rpm | head -14
* Wed Mar 19 2003 Jakub Jelinek <jakub@xxxxxxxxxx> 2.3.2-4.80
- build as 8.0 errata
- turn compatibility only symbols which are referenced in libc.so's
relocations back into @@ symvers, as otherwise statically linked
RHL 8 apps segfault when doing NSS or iconv
- move __libc_fork, __libc_stack_end, __libc_wait and __libc_waitpid
from GLIBC_PRIVATE symver for the errata
- remove {INIT,PREINIT,FINI}_ARRAY support, since it requires
binutils changes
- don't build NPTL libraries
- strip libraries and binaries, recreate glibc-debug-static
subpackage
Regards,
Bill Rugolsky
--
Psyche-list mailing list
Psyche-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/psyche-list
