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>
This commit is contained in:
parent
709ba3c465
commit
9bcee1f034
1 changed files with 4 additions and 1 deletions
|
|
@ -34,8 +34,11 @@
|
||||||
* 0100000 in the kernel) at each file open. FUSE is all too
|
* 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
|
* happy to pass the flag onto us, where we'd have no idea what
|
||||||
* to do with it if we trusted glibc.
|
* 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
|
# undef O_LARGEFILE
|
||||||
# define O_LARGEFILE 0100000
|
# define O_LARGEFILE 0100000
|
||||||
#endif
|
#endif
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue