https://svn.boost.org/trac10/ticket/13230 <p> Behavior of <code>_FILE_OFFSET_BITS</code> in Android NDK is described at android.googlesource.com/platform/bionic/+/master/docs/32-bit-abi.md </p> <blockquote class="citation"> <p> Android support for <code>_FILE_OFFSET_BITS=64</code> (which turns off_t into <code>off64_t</code> and replaces each <code>off_t</code> function with its <code>off64_t</code> counterpart, such as <code>lseek</code> in the source becoming <code>lseek64</code> at runtime) was added late. Even when it became available for the platform, it wasn‘t available from the NDK until r15. Before NDK r15, <code>_FILE_OFFSET_BITS=64</code> silently did nothing: all code compiled with that was actually using a 32-bit <code>off_t</code>. With a new enough NDK, the situation becomes complicated. If you’re targeting an API before 21, almost all functions that take an <code>off_t</code> become unavailable. You‘ve asked for their 64-bit equivalents, and none of them (except <code>lseek</code>/<code>lseek64</code>) exist. As you increase your target API level, you’ll have more and more of the functions available. API 12 adds some of the <code>&lt;unistd.h&gt;</code> functions, API 21 adds mmap, and by API 24 you have everything including <code>&lt;stdio.h&gt;</code>. </p> </blockquote> <p> In <code>filesystem/src/operations.cpp</code> <code>_FILE_OFFSET_BITS</code> is unconditionally defined to <code>64</code> in hope that </p> <blockquote class="citation"> <p> at worst, these defines may have no effect </p> </blockquote> <p> It actually breaks compilation with Android NDK r15 if <code>__ANDROID_API__</code> is less than 24. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13230 Trac 1.4.3 joerg@… Thu, 07 Dec 2017 12:48:48 GMT