t9pfuse: Disable glibc workaround for O_LARGEFILE on ARM - plan9port - [fork] Plan 9 from user space
 (HTM) git clone git://src.adamsgaard.dk/plan9port
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) README
 (DIR) LICENSE
       ---
 (DIR) commit 9bcee1f034af98a7226e56e346c2cbe3d6a7b325
 (DIR) parent 709ba3c4652b7a72554cb0e13d7e64bda8d0287e
 (HTM) Author: Merlijn Wajer <merlijn@wizzup.org>
       Date:   Wed, 19 Nov 2014 00:30:46 +0100
       
       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 <rsc@swtch.com>
       
       Diffstat:
         M src/cmd/9pfuse/main.c               |       5 ++++-
       
       1 file changed, 4 insertions(+), 1 deletion(-)
       ---
 (DIR) diff --git a/src/cmd/9pfuse/main.c b/src/cmd/9pfuse/main.c
       t@@ -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