summaryrefslogtreecommitdiff
path: root/Versions.def
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2013-09-02 23:13:57 -0400
committerMike Frysinger <vapier@gentoo.org>2013-09-02 23:22:24 -0400
commit18d4371683fbe347bf4fbaef05d18b5a4918887a (patch)
treedae8b09c9b587cf61d88825080cd36510182e8ae /Versions.def
parentac44401205b9b2da48ce5bdb0bd772df8bf2df4b (diff)
downloadglibc-18d4371683fbe347bf4fbaef05d18b5a4918887a.tar.gz
hppa: add fanotify_mark
Another example of all the 64bit arches getting the definition via a common file, but the 32bit ones all adding it by themselves and hppa was missed. I'm not entirely sure about the usage of GLIBC_2.19 symbols here. We'd like to backport this so people can use it, but it means we'd be releasing a glibc-2.17/glibc-2.18 with a GLIBC_2.19 symbol in it. But maybe it won't be a big deal since you'd only get that 2.19 ref if you actually used the symbol ? There hasn't been a glibc release where hppa worked w/out a bunch of patches, so in reality there's only two distros that matter -- Gentoo and Debian. Reported-by: Jeroen Roovers <jer@gentoo.org> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'Versions.def')
-rw-r--r--Versions.def1
1 files changed, 1 insertions, 0 deletions
diff --git a/Versions.def b/Versions.def
index 0854e6eb3b..bca4ff44e0 100644
--- a/Versions.def
+++ b/Versions.def
@@ -35,6 +35,7 @@ libc {
GLIBC_2.16
GLIBC_2.17
GLIBC_2.18
+ GLIBC_2.19
HURD_CTHREADS_0.3
%ifdef EXPORT_UNWIND_FIND_FDE
GCC_3.0