<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 Jul 1, 2015, at 3:07 PM, 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"><br class=""><div class="gmail_quote">On 1 July 2015 at 19:24, Khem Raj <span dir="ltr" class=""><<a href="mailto:raj.khem@gmail.com" target="_blank" class="">raj.khem@gmail.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=":19g" class="a3s" style="overflow:hidden">Make error() portable, Fix build on musl<br class=""></div></blockquote></div><br class="">Upstream points out that theres lots of other GNU-specific bits in Weston (such as gnu-specific printf formats). Does musl support those or is this a token step towards being musl-friendly?</div><div class="gmail_extra"><br class=""></div></div></div></blockquote><div><br class=""></div><div>No, certain construct like %m which are used in weston are already part of musl. As of now it builds and boots fine with latest musl release and we will address any future issues</div><div>if they arise. moreover upstream wayland/weston is very receptive for musl changes. Now regarding this patch, I will redo it and submit it upstream to incorporate the feedback,</div><div>however the patch itself is ok its just the mechanics of it which needs to be changed.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra">Ross</div></div>
</div></blockquote></div><br class=""></body></html>