<div dir="ltr">On Thu, Aug 1, 2013 at 6:02 PM, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@linux.intel.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><span style="color:rgb(34,34,34)">I'm afraid this is not practical. The ability to specify the value for MACHINE</span><br>
</div></div>
and other variables from the external environment is not just there for folks<br>
running bitbake manually from the command line, but also external scripts as<br>
well, and they could quite legitimately set it to the same value that has been<br>
specified in the configuration file and showing a warning in that case would be<br>
undesirable.<br></blockquote><div><br></div><div>Oh yeah, it cannot happen with compiler outputs the same way? Answer is: it can.</div><div><br></div><div>You can add another feature later though if you wish to suppress warnings. That makes sense to me.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'm not sure I understand the value of showing this warning in any case. The<br>
system is not going to do anything that the user won't expect - the user<br>
specified the value of MACHINE on the command line and that's the value that is<br>
being used. The fact that it is the same as what's in the configuration file is<br>
incidental.<br></blockquote><div><br></div><div>Have you used gcc, clang, etc? Do you have experience with warnings in general? They are there in certain cases because the programmer may have or probably made a mistake. It is a lot easier to figure out at that time than debugging very hard later...</div>
<div><br></div><div>Actually, it is even getting more serious in your "script" case where it would be totally hidden by the script if it is not logging properly, and you would only realize an issue later.</div><div>
<br></div><div>Surely, we all copy paste wrong on a daily basis, and we also write "foo" instead "fow" and "bar" at times. So, I do not follow your comment. Nothing to reinvent the wheel here, just follow the general practice that other software developers have figured out along the decades.</div>
</div></div></div>