| commit | 18d4371683fbe347bf4fbaef05d18b5a4918887a | |
| author | Mike Frysinger <vapier@gentoo.org> | |
| Tue, 3 Sep 2013 03:13:57 +0000 (2 23:13 -0400) | ||
| committer | Mike Frysinger <vapier@gentoo.org> | |
| Tue, 3 Sep 2013 03:22:24 +0000 (2 23:22 -0400) | ||
| tree | dae8b09c9b587cf61d88825080cd36510182e8ae | treesnapshot (tar.gz zip) |
| parent | ac44401205b9b2da48ce5bdb0bd772df8bf2df4b | commitdiff |
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>
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>