<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 17 Oct 2012, at 14:54, Jonas Maebe 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: Monaco; 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; "><span class="Apple-style-span" style="font-family: monospace; ">I think it's annoying that you then have to type OVERRIDEVERSIONCHECK=1 whenever you build a cross-compiler. Even more: it will suggest that building a cross-compiler should also be done starting with the latest release, while in fact it they should be built using a native compiler built from the same svn version. Therefore I don't think think that we can check anything in case of cross-building.<br></span></span></blockquote></div><br><div>Also, maybe the printed message should be more explicit about the fact that using the latest release is the only supported way to bootstrap the compiler, and that <span class="Apple-style-span" style="font-family: monospace; ">OVERRIDEVERSIONCHECK=1 must only be used if you know for a fact that the starting compiler was built from the same sources that you are currently compiler</span>.</div><div><span class="Apple-style-span" style="font-family: monospace; "><br></span></div><div><span class="Apple-style-span" style="font-family: monospace; "><br></span></div><div><span class="Apple-style-span" style="font-family: monospace; ">Jonas</span></div></body></html>