summaryrefslogtreecommitdiff
path: root/system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch
diff options
context:
space:
mode:
Diffstat (limited to 'system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch')
-rw-r--r--system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch23
1 files changed, 19 insertions, 4 deletions
diff --git a/system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch b/system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch
index 33b0d2379..21958a650 100644
--- a/system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch
+++ b/system/musl/0003-pathconf-add-_PC_TIMESTAMP_RESOLUTION.patch
@@ -1,7 +1,7 @@
-From da7bab19d59a0ea50e23371462f688329cd6c1a7 Mon Sep 17 00:00:00 2001
+From 1d486ac55014c39f225f12bac80202197c2bf9c6 Mon Sep 17 00:00:00 2001
From: "A. Wilcox" <AWilcox@Wilcox-Tech.com>
Date: Wed, 11 Apr 2018 23:43:19 -0500
-Subject: [PATCH 3/3] pathconf: add _PC_TIMESTAMP_RESOLUTION
+Subject: [PATCH 3/7] pathconf: add _PC_TIMESTAMP_RESOLUTION
Right now, this is a worst-case assumption; some kernels may actually
have a value of 100000 here (100 Hz timers). This is considered the
@@ -9,8 +9,9 @@ easiest implementation.
This is required to be present in <unistd.h>.
---
- include/unistd.h | 1 +
- 1 file changed, 1 insertion(+)
+ include/unistd.h | 1 +
+ src/conf/fpathconf.c | 3 ++-
+ 2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/unistd.h b/include/unistd.h
index 68686dfd..1bdd3292 100644
@@ -24,6 +25,20 @@ index 68686dfd..1bdd3292 100644
#define _SC_ARG_MAX 0
#define _SC_CHILD_MAX 1
+diff --git a/src/conf/fpathconf.c b/src/conf/fpathconf.c
+index 8eb037e6..1eefac18 100644
+--- a/src/conf/fpathconf.c
++++ b/src/conf/fpathconf.c
+@@ -25,7 +25,8 @@ long fpathconf(int fd, int name)
+ [_PC_REC_XFER_ALIGN] = 4096,
+ [_PC_ALLOC_SIZE_MIN] = 4096,
+ [_PC_SYMLINK_MAX] = SYMLINK_MAX,
+- [_PC_2_SYMLINKS] = 1
++ [_PC_2_SYMLINKS] = 1,
++ [_PC_TIMESTAMP_RESOLUTION] = 1000000,
+ };
+ if (name >= sizeof(values)/sizeof(values[0])) {
+ errno = EINVAL;
--
2.15.0