In message [off-list ref] you wrote:
I reckon my app does not support large files. Since after writing 2GB
to a file
Did you build it with the required options, like #defining
_FILE_OFFSET_BITS as 64 ?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You are only young once, but you can stay immature indefinitely.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Wolfgang Denk wrote:
In message [off-list ref] you wrote:
quoted
I reckon my app does not support large files. Since after writing 2GB
to a file
Did you build it with the required options, like #defining
_FILE_OFFSET_BITS as 64 ?
Nope!
But good point! :o)
And I just got these lines:
Fillod Stephane wrote:
> Recent kernel and glibc are fine.
>
> Pass O_LARGEFILE to the second open() arg, and compile
> with "-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" should do it.
and rebuilt my application. But the test (with my app) will take a
while...
Thanks!
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
I wrote:
And I just got these lines:
Fillod Stephane wrote:
> Recent kernel and glibc are fine.
>
> Pass O_LARGEFILE to the second open() arg, and compile
> with "-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" should do it.
and rebuilt my application. But the test (with my app) will take a
while...
Now I the app is still running although the file is > 2GB. I get
~ # ls -l /mnt/intern/HDD_STRESS/2003-07-31\ 1*
/mnt/intern/HDD_STRESS/2003-07-31 14-54-57 (1):
ls: /mnt/intern/HDD_STRESS/2003-07-31 14-54-57 (1)/V001_G0.raw: Value
too large for defined data type
-rw-r--r-- 1 root root 1080356864 Jul 31 16:25 K001_G0.raw
-rw-r--r-- 1 root root 1080356864 Jul 31 16:25 K002_G0.raw
I guess I have to rebuild busybox with LFS as well...
Thanks to you all!
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/