From 9bcee1f034af98a7226e56e346c2cbe3d6a7b325 Mon Sep 17 00:00:00 2001 From: Merlijn Wajer Date: Wed, 19 Nov 2014 00:30:46 +0100 Subject: 9pfuse: Disable glibc workaround for O_LARGEFILE on ARM 9pfuse fails on ARM when O_LARGEFILE is supported. glibc does define O_LARGEFILE properly on ARM, and the value is different than what that this workaround suggests, causing it to wrongly detect bad flags. Change-Id: I02b0cc222ca7785c4b1739c3df3caa17cf7bc265 Reviewed-on: https://plan9port-review.googlesource.com/1094 Reviewed-by: Russ Cox --- src/cmd/9pfuse/main.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'src/cmd/9pfuse') diff --git a/src/cmd/9pfuse/main.c b/src/cmd/9pfuse/main.c index 8fa56ff4..cbce3ffd 100644 --- a/src/cmd/9pfuse/main.c +++ b/src/cmd/9pfuse/main.c @@ -34,8 +34,11 @@ * 0100000 in the kernel) at each file open. FUSE is all too * happy to pass the flag onto us, where we'd have no idea what * to do with it if we trusted glibc. + * + * On ARM however, the O_LARGEFILE is set correctly. */ -#if defined(__linux__) + +#if defined(__linux__) && !defined(__arm__) # undef O_LARGEFILE # define O_LARGEFILE 0100000 #endif -- cgit v1.2.3