This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Notice clock_* functions in librt.so for old GLIBC_2.18 builds?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Andreas Jaeger <aj at suse dot com>, Michael Matz <matz at suse dot de>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, Adam Conrad <adconrad at 0c3 dot net>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>
- Date: Fri, 21 Feb 2014 02:28:41 -0500
- Subject: Notice clock_* functions in librt.so for old GLIBC_2.18 builds?
- Authentication-results: sourceware.org; auth=none
I'm bootstrapping a Fedora ppc64le build from GLIBC_2.18
to GLIBC_2.17 default ABI and I noticed something odd.
Did any of you notice clock_* functions in librt.so
when you were doing GLIBC_2.18 ABI builds of ppc64le?
For a port like this starting at GLIBC_2.17 or
GLIBC_2.18 there should be no clock_* functions in
librt.so.
The conditional is:
#if SHLIB_COMPAT (librt, GLIBC_2_2, GLIBC_2_17)
Which should result in no code if the ABI starts at
GLIBC_2_17 or later.
It was almost as if some of our shlib-compat macros
or scripts didn't work correctly when the baseline
ABI was greater than the obsoleted ABI?
I've run out of time tonight to rebuild again with
the GLIBC_2.18 ABI to double check, but I figured one
of you might be able to do that before I get up again.
Cheers,
Carlos.