<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 17, 2012, at 4:38 AM, Jorge Almeida 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; ">Both have toolchains that are newer than the<br>recommended versions...</span></blockquote></div><div><br></div><div>I'd recommend CLFS dev and not 1.2.0 as dev has been pretty stable for half a year or more and is about to be released. We are in a package freeze. Builds have been successful, and ironing out some arch specific issues like boot loaders mostly. If you insist to use 1.2.0, newer hosts will build that as well. When you do encounter an issue, search mailing lists through the internet for any issues that you will encounter. I have an updated lfs livecd you can use , and I use it to build CLFS dev builds just fine. It ill build 1.0.0 and 1.2.0 just fine.</div><div><br></div><div><a href="http://cross-lfs.org/~kb0iic/livecdupd/">http://cross-lfs.org/~kb0iic/livecdupd/</a></div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>