You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug stat can fail on 32bit systems if not compiled with -D_FILE_OFFSET_BITS=64.
That could be because inode number is too large (happens on many file systems) or the file itself is too large.
I don't know why it was apparently removed because of Android builds (cmake check for android not working)?
But for 32bit armhf this is needed for sure.
To Reproduce
Try reading a file with assimp on armhf (or probably any other 32bit arch) which has a inode number not representable in 32bit.
E.g. from a NFS mount or XFS file system.
Expected behavior DefaultIOStream::FileSize() returns correct size instead of 0.
Platform (please complete the following information):
- Reenable fix to ensure that stat works correctly on 32-bit linuxes again
- stat will return 32-bit inodes when checking a file. So when this call will be used on a 64-bit linux this will cause errors like:
Error writing to foo: Value too large for defined data type
File I/O error: foo
- closes#4390
Describe the bug
stat
can fail on 32bit systems if not compiled with-D_FILE_OFFSET_BITS=64
.That could be because inode number is too large (happens on many file systems) or the file itself is too large.
This was
I don't know why it was apparently removed because of Android builds (cmake check for android not working)?
But for 32bit armhf this is needed for sure.
To Reproduce
Try reading a file with assimp on armhf (or probably any other 32bit arch) which has a inode number not representable in 32bit.
E.g. from a NFS mount or XFS file system.
Expected behavior
DefaultIOStream::FileSize()
returns correct size instead of 0.Platform (please complete the following information):
Additional context
Might be the (or at least one) cause for autopkgtests failing for 32bit archs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995859
The text was updated successfully, but these errors were encountered: