shlib-compat.h
Andreas Jaeger
aj@suse.de
Tue Mar 21 13:51:00 GMT 2000
>>>>> Roland McGrath writes:
> I have implemented some changes to better manage symbol version sets and
> old-versioned ABI compatibility code. The intent of these changes is that
> when a port to a new platform is done or a library's soname gets changed,
> libraries built for the new platform/soname not pay the overhead to support
> obsolete symbol versions that were never supported before by that soname on
> that platform.
> I control this with a new (optional) parameter in shlib-versions that gives
> the earliest symbol version set that needs to be supported. This has two
> effects:
Hi Roland,
I didn't look closely at your patches yet - the description sounds
excellent. Ralf and I discussed one enhancement which we could
use for MIPS/Linux: Ignore a version in between. MIPS/Linux uses
currently glibc 2.0.7 - and the next supported version should be (I
hope) glibc 2.2. glibc 2.1 might not be supported at all.
Is this possible to add?
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
More information about the Libc-hacker
mailing list