<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 23, 2015 at 5:47 AM, Otavio Salvador <span dir="ltr"><<a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Jan 23, 2015 at 12:12 AM, Robert Yang <<a href="mailto:liezhi.yang@windriver.com">liezhi.yang@windriver.com</a>> wrote:<br>
> We have several GPLv2 recipes such as <a href="http://m4-native_1.4.9.bb" target="_blank">m4-native_1.4.9.bb</a>, while we also<br>
> have GPLv3's <a href="http://m4-native_1.4.17.bb" target="_blank">m4-native_<span class="aBn"><span class="aQJ">1.4.17</span></span>.bb</a>, I think that we can remove<br>
> <a href="http://m4-native_1.4.9.bb" target="_blank">m4-native_1.4.9.bb</a> if the target <a href="http://m4_1.4.9.bb" target="_blank">m4_1.4.9.bb</a> builds well ?<br>
><br>
> I'd like to remove it because we don't build the lower native version by<br>
> default, and we don't know whether it works or when it would fail.<br>
<br>
</span>I second this; not tested recipes are always good to remove.</blockquote></div><br>The one case I'd be concerned with is where a native tool is used to crosscompile something for the target, specifically in the case of scripting tools which often have implicit dependency on the exact same version, so it can parse what it needs to parse to build. Python for example, I doubt you'd want to try to use 2.4 as part of the 2.7 crosscompilation process. m4 being a scripting language, that might be the case here. Of course, if the language is compatible between the two versions, maybe that's a non-issue.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>