Update on freeze status of glibc 2.18?

[Richard Henderson]

On 06/21/2013 10:47 AM, Andi Kleen wrote:
> I'm not sure the linker failure will be any more comprehensible to
> the user than the assert.

Certainly it is.  Consider the following example, built on F19 (glibc 2.17) and
run on F18 (glibc 2.16):

#include <time.h>
void *x = clock_nanosleep;
int main() { return 0; }

$ ./z1
./z1: /lib64/libc.so.6: version `GLIBC_2.17' not found (required by ./z1)

Given that we've used sensible names for our versions, I think that error
message is crystal clear.


r~