[csw-maintainers] Calling statvfs() on my home directory

[Maciej (Matchek) Blizinski]

As Dago suggested, adding the output of getconf LFS_CFLAGS to CFLAGS
fixes the statvfs() issue.  It expands to:

-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

Outcome:

Running: cc -m32 statvfs-example.c -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -o statvfs-example-32
statvfs-example-32:     ELF 32-bit LSB executable 80386 Version 1
[FPU], dynamically linked, not stripped
statvfs() completed successfully.
Running: cc -m64 statvfs-example.c -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -o statvfs-example-64
statvfs-example-64:     ELF 64-bit LSB executable AMD64 Version 1 [SSE
FXSR FPU], dynamically linked, not stripped
statvfs() completed successfully.

I don't yet have a proof, but I think that our perl might not handle
statvfs() well.  Does anyone know what perl functionality causes the
statvfs() call to be made?