<div dir="ltr"><div class="gmail_extra">CCing openembedded-architecture to open the field for comments.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On 7 March 2017 at 04:58, Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id="gmail-:2m3" class="gmail-a3s gmail-aXjCH gmail-m15aa722cead5dc11">The largefile distro feature has been enabled by default in oe-core<br>
for a long time and, more recently, also in poky-tiny. Building<br>
without the largefile distro feature receives little or no testing.<br>
Many packages now enable LFS without exposing a configure option, so<br>
there should be very little expectation that disabling the distro<br>
feature will result in a distro which globally disables LFS.<br></div></blockquote></div><br>So I've had a bug for this for some time but have never got around to it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">If we're going to assert "LFS by default" do we want a sanity check to verify it was used?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Do we want to put <span style="font-size:12.800000190734863px">-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 in the default CFLAGS?</span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px"><br></span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px">I'm not aware of any good reason to not use LFS, but now is the time for anyone else to speak up if you have a good reason to keep it as an option!</span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px"><br></span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px">Ross</span></div></div>