This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] change GLIBC PPC64/ELF2 ABI default to 2.17


> Yes, but so what?  If you're providing glibc 2.17, you provide the symbols
> that came with 2.17.  The version tag on those symbols doesn't mean you're
> providing glibc 2.18 (or 2.19), it just means you're pulling tricks to
> provide @2.18 symbols on a 2.17 build.

It means that if you build an app against 2.19+ and use the new symbols,
then you get an executable that requires GLIBC_2.19 and package-system
dependencies that know it requires GLIBC_2.19.  Then you can install this
on your backport-based system, and the package dependencies will look fine,
and the version set dependencies checked at startup will look fine, but
lazy PLT lookup of a new symbol makes the program abort somewhere in the
middle of its run.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]