<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div>On Aug 16, 2013, at 2:48 PM, William Harrington wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">They also don't do a cross compile.</span></blockquote></div><br><div>Rather they don't do a cross toolchain. Then build LFS from that toolchain.</div><div><br></div><div>It's a fake cross tools. when the target triplet changes then cross tools is detected. It's the only way to build LFS the way they want to without introducing complexity in their build system.</div><div><br></div><div>Matter of fact, you can have your own target triplet, in which cross compilation isn't there, but it is a build toolchain, and you can use that build toolchain throughout your whole build.</div><div><br></div><div>limits.h is for the target.</div><div><br></div><div>If limits.h is wrong, then the target was built wrong.</div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>