This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] change GLIBC PPC64/ELF2 ABI default to 2.17
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Adam Conrad <adconrad at 0c3 dot net>
- Cc: munroesj at us dot ibm dot com, Brooks Moses <brooks dot moses at dpdx dot net>, libc-alpha at sourceware dot org, carlos at redhat dot com
- Date: Fri, 31 Jan 2014 13:59:27 -0800 (PST)
- Subject: Re: [PATCH] change GLIBC PPC64/ELF2 ABI default to 2.17
- Authentication-results: sourceware.org; auth=none
- References: <20140131201607 dot GG99202 at jinx> <1391202081 dot 1683 dot 17 dot camel at spokane1 dot rchland dot ibm dot com> <20140131213241 dot GP15976 at 0c3 dot net>
> 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.