microblaze: don't use copy_file_range syscall with kernel headers < 4.10

copy_file_range syscall was added for microblaze in 4.10.

This patch makes the MicroBlaze kernel-features.h undefine
__ASSUME_COPY_FILE_RANGE for toolchains built with kernel headers < 4.10.

	* sysdeps/unix/sysv/linux/microblaze/kernel-features.h
	(__ASSUME_COPY_FILE_RANGE) [__LINUX_KERNEL_VERSION < 0x040A00]: Undef.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=7181e5590e5ba898804aef3ee6be7f27606e6f8b

Signed-off-by: Romain Naour <romain.naour@gmail.com>
This commit is contained in:
Romain Naour 2018-01-29 16:12:08 +00:00 committed by Joseph Myers
parent e3aa6999d7
commit b7ccb5de35
2 changed files with 10 additions and 0 deletions

View File

@ -1,3 +1,8 @@
2018-01-29 Romain Naour <romain.naour@gmail.com> (tiny change)
* sysdeps/unix/sysv/linux/microblaze/kernel-features.h
(__ASSUME_COPY_FILE_RANGE) [__LINUX_KERNEL_VERSION < 0x040A00]: Undef.
2018-01-29 Joseph Myers <joseph@codesourcery.com>
* scripts/build-many-glibcs.py (Context.git_checkout): Use git

View File

@ -52,3 +52,8 @@
#if __LINUX_KERNEL_VERSION < 0x040000
# undef __ASSUME_EXECVEAT
#endif
/* Support for the copy_file_range syscall was added in 4.10. */
#if __LINUX_KERNEL_VERSION < 0x040A00
# undef __ASSUME_COPY_FILE_RANGE
#endif