<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 29, 2013, at 9:20 AM, Martin Ward 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; ">Just had a quick look into this, i don't think it matters in our context it seems to set an environment variable NATIVE_SYSTEM_HEADERS, but CROSS_SYSTEM_HEADERS is always set to /tools/include which ever way the switch is set<br><br>i suppose it won't hurt --with-system-native-header-dir=/tools/include for consistency<br><br>opinions ?</span></blockquote></div><br><div>I'll update my working book and right now I'm doing a powerpc target build and will look into the issues with gawk during cross compile.</div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>