This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Symbol versioning question..
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Marcus Shawcroft <marcus dot shawcroft at linaro dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 19 Jul 2013 15:52:22 +0200
- Subject: Re: Symbol versioning question..
- References: <CABXK9ndVsUhXdx5YfV+NDSa99daV9wJtj1ucMAxcH6zQmbChqg at mail dot gmail dot com>
One problem with the abi check is that there is currently no check that
all expected interfaces are actually present in the abi lists, which has
biten us in the past already (like the absence of fallocate64 on all
32-bit archs in 2.10).
Generally, once a version is released the ABI is frozen, no further
additions or changes are possible. So the only option you have is to
make sure that there will be no mount@GLIBC_2.17 on aarch64 and add it
to GLIBC_2.18. To do that you need to move the symbol out of the
generic Versions files into more specific ones that are not seen by
aarch64.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."