On 2023-06-17 12:53, matoro via GNU coreutils Bug Reports wrote:
Compiling with -D_FILE_OFFSET_BITS=64 fixes the problem.
Thanks for checking. I installed the following fix to coreutils:
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=5ac7f2d281ef70500fc70211dc1f146c8666e8c1
This
On 2023-06-17 15:23, Paul Eggert wrote:
On 2023-06-17 10:30, Pádraig Brady wrote:
I see that s390 and alpha are the only 64 bit architectures
that have a 32-bit ino_t for example, which may cause issues within
glibc?
Weird.
What happens if you compile with -D_FILE_OFFSET_BITS=64? Does this
On 2023-06-17 15:19, Pádraig Brady wrote:
In case it's useful, I noticed this thread from 2014 about ino_t
and consequences of using -D_FILE_OFFSET_BITS=64
https://sourceware.org/pipermail/libc-alpha/2014-March/thread.html#49675
Yes, that was about glibc. For Autoconf and Gnulib it's long been
On 17/06/2023 20:53, matoro wrote:
On 2023-06-17 15:23, Paul Eggert wrote:
On 2023-06-17 10:30, Pádraig Brady wrote:
I see that s390 and alpha are the only 64 bit architectures
that have a 32-bit ino_t for example, which may cause issues within
glibc?
Weird.
What happens if you compile with
On 2023-06-17 10:30, Pádraig Brady wrote:
I see that s390 and alpha are the only 64 bit architectures
that have a 32-bit ino_t for example, which may cause issues within glibc?
Weird.
What happens if you compile with -D_FILE_OFFSET_BITS=64? Does this cause
alpha to have a 64-bit ino_t? (How
On 17/06/2023 00:55, matoro via GNU coreutils Bug Reports wrote:
Hi, when running the command "stat -f -c '%T' ." on an alpha while being
on an NFS filesystem, the command fails with EOVERFLOW.
$ stat -f -c "%T" .
stat: cannot read file system information for '.': Value too large for
defined
Hi, when running the command "stat -f -c '%T' ." on an alpha while being
on an NFS filesystem, the command fails with EOVERFLOW.
$ stat -f -c "%T" .
stat: cannot read file system information for '.': Value too large for
defined data type
The command does NOT fail when targeting any other
