[Toybox] [PATCH] Avoid copy_file_range(2) on Android.

[enh]

Strictly we could use it if the target API level is high enough,
but that would mean that you couldn't safely run the resulting
binary on an older Android release, and anecdotally I don't think
people are that careful.

The obvious alternative would be to install a signal handler for
SIGSYS so we can probe for copy_file_range(2) at runtime rather
than compile time, but it's not obvious to me that it matters enough?
---
 lib/portability.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.landley.net/pipermail/toybox-landley.net/attachments/20220613/ae7458e3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Avoid-copy_file_range-2-on-Android.patch
Type: application/octet-stream
Size: 1452 bytes
Desc: not available
URL: <http://lists.landley.net/pipermail/toybox-landley.net/attachments/20220613/ae7458e3/attachment-0001.obj>