_FILE_OFFSET_BITS why this?

Denis Vlasenko vda.linux at googlemail.com
Sun Dec 10 02:24:22 UTC 2006


On Monday 04 December 2006 11:31, Thomas Fröhlich wrote:
> Hi!
> 
> I will compile the svn version, but in the last days I have some 
> problems. :(
> My GCC is arm-linux-uclibc-gcc (GCC) 3.3.3
> My make command, after some trys: 'make ARCH=arm 
> CROSS_COMPILE=/usr/local/src/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-'
> 
> all will compile nice until:
>   CC      util-linux/more.o
> util-linux/more.c:107:5: "_FILE_OFFSET_BITS" is not defined
> make[1]: *** [util-linux/more.o] Error 1
> make: *** [util-linux] Error 2
> 
> Why is _FILE_OFFSET_BITS for arm important?
> 
> in the file is 
> 
> #if _FILE_OFFSET_BITS == 64
> len += printf("(%d%% of %lld bytes)",
> (int) (100 * ((double) ftell(file) /
> (double) st.st_size)), (long long)st.st_size);
> #else
> len += printf("(%d%% of %ld bytes)",
> (int) (100 * ((double) ftell(file) /
> (double) st.st_size)), (long)st.st_size);
> #endif
> 
> but it's the same to 1.2.0.
> 
> in Makefile.flags:15:      $(if $(CONFIG_LFS),-D_LARGEFILE_SOURCE 
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64)
> 
> is this right?

Fallout from -Wundef. Fixed in svn, thanks.
--
vda



More information about the busybox mailing list