<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 2, 2015, at 9:26 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" class="">ross.burton@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">Armin,</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 2 February 2015 at 16:41, akuster <span dir="ltr" class=""><<a href="mailto:akuster@mvista.com" target="_blank" class="">akuster@mvista.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":55" class="a3s" style="overflow:hidden">If I knew what "testing' entailed I would through some time at this.<br class=""></div></blockquote><div class=""><br class=""></div><div class="">"Please build your stuff with this glibc/gcc and check it still works".</div><div class=""><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>anything helps. apply the patches and see if they apply and parse correctly with your layer combo</div><div>then second step is compile and build images/sdks as Ross said.</div><div>Third would be boot and runt the images and workloads which you normally do</div><div>4th would be run your tests</div><div>5th would be run gcc and glibc unit tests.</div><div>and repeat same for as many architectures as possible.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Ross</div></div></div></div>
</div></blockquote></div><br class=""></body></html>