Bug 2525 - dosfstools limits dos filesystems to 2GB
Summary: dosfstools limits dos filesystems to 2GB
Status: RESOLVED OBSOLETE
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low minor
Target Milestone: 1.7
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
: 3779 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-05-31 03:19 UTC by Seebs
Modified: 2014-06-23 18:15 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Seebs 2012-05-31 03:19:15 UTC
The CFLAGS passed in by Yocto override the -D_FILE_OFFSET_BITS=64 in the Makefile, which causes dosfstools to end up only supporting 2GB filesystems.  Workaround is to pass that in via CFLAGS_append.

Spotted by mebrown in #yocto, who's on a crunch schedule and hasn't got time to file a formal report.

(The -D_FILE_OFFSET_BITS=64 is in OPTFLAGS, which is shoved into CFLAGS in the makefile.  I am not sure it should have been considered an optmitization flag to begin with, but...)
Comment 1 Nitin Kamble 2013-01-24 21:44:29 UTC
*** Bug 3779 has been marked as a duplicate of this bug. ***
Comment 2 Eddy Lai 2013-01-28 13:35:57 UTC
is the workaround to put 
CFLAGS_append="-D_FILE_OFFSET_BITS=64"
in the conf/local.conf then build the image?
I have tried to use
IMAGE_ROOTFS_EXTRA_SPACE = "1048576"
to create a ~1.5GB image, but same failed to boot from USB flash disk.
Comment 3 Darren Hart 2013-01-28 17:28:51 UTC
I believe you would to add something along those lines to a bbappend for the dosfstools recipe, not to local.conf. You can verify by viewing the compile step logs for the package.
Comment 4 Darren Hart 2013-02-28 05:12:48 UTC
Eddy, have you had a chance to try the workaround?
Comment 5 Richard Purdie 2014-06-03 11:24:24 UTC
The recipe now contains this line, no feedback from the reporter for a couple of years so closing as obsolete, suspected resolved. Reopen if the are still issues.