I recently had to enable _FILE_OFFSET_BITS=64 to support 2GB+ files in FBNeo and noticed it broke file operation on android 32-bits.
After investigation the reason was that the fseeko/ftello functions used in https://github.com/libretro/libretro-common/blob/master/vfs/vfs_implementation.c don't exist with buildbot's default api level.
Things went back to normal after forcing a higher android api level (24). maybe the codepath in vfs_implementation.c could be improved by checking the api level.
64-bits android buildbot was never affected because i think it uses a higher default api level. To avoid this kind of discrepancies, maybe the default api level for the 32-bits android buildbot should just be bumped to the same level as the 64-bits one.
I recently had to enable
_FILE_OFFSET_BITS=64to support 2GB+ files in FBNeo and noticed it broke file operation on android 32-bits.After investigation the reason was that the
fseeko/ftellofunctions used in https://github.com/libretro/libretro-common/blob/master/vfs/vfs_implementation.c don't exist with buildbot's default api level.Things went back to normal after forcing a higher android api level (24). maybe the codepath in
vfs_implementation.ccould be improved by checking the api level.64-bits android buildbot was never affected because i think it uses a higher default api level. To avoid this kind of discrepancies, maybe the default api level for the 32-bits android buildbot should just be bumped to the same level as the 64-bits one.