On 9/29/22 00:15, Eduard Bloch wrote:
[*] _LARGEFILE_SOURCE or _FILE_OFFSET_BITS=64
Both of them? I don't think so. _LARGEFILE_SOURCE will export some XYZo
functions of the C API, but I don't use them.
Ok.
....
apt-cacher-ng has been adding those defines since
the early days of its creation.
Really?
I don't find the CFLAGS _LARGEFILE_SOURCE or _FILE_OFFSET_BITS=64 in the
sources.
Strange, my grep command has no problems doing right that.
$ grep FILE_OFFSET src/* CMakeLists.txt
src/config.h:// added in Makefile... #define _FILE_OFFSET_BITS 64
src/meta.h:// _FILE_OFFSET_BITS mostly irrelevant. But if it's set, watch out for user's
"experiments".
src/meta.h:#if _FILE_OFFSET_BITS == 32
src/meta.h:#error Unsupported: _FILE_OFFSET_BITS == 32 with large long size
src/meta.h:#if 64 == _FILE_OFFSET_BITS
src/meta.h:#if 32 == _FILE_OFFSET_BITS
CMakeLists.txt:SET(ACNG_COMPFLAGS "-D_FILE_OFFSET_BITS=64")
You are absolutely right!
I have no idea why I didn't find them too.
Maybe I grepped the wrong directory, maybe only for _LARGEFILE_SOURCE?
Anyway, I agree _FILE_OFFSET_BITS is set.
I opened the bug because I faced this cronjob-error sometimes:
/etc/cron.daily/apt-cacher-ng:
Aborted
run-parts: /etc/cron.daily/apt-cacher-ng exited with return code 134
I assumed it's because of lfs, but it's probably something else.
Helge
