<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 1, 2013 at 1:58 PM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1 August 2013 12:18, Laszlo Papp <<a href="mailto:lpapp@kde.org">lpapp@kde.org</a>> wrote:<br>
>> It cannot be more specific without dumping the entire machine<br>
>> configuration, which won't help because a variable is *not* set.<br>
><br>
> No no, it could print out the concrete file to look up, not just a name.<br>
> Besides, I would probably even print a warning about the entry point and<br>
> load address not set.<br>
<br>
</div>This is a simple "can I even build?" check, and UBOOT_MACHINE is sufficient.<br>
<br>
Our users are not totally useless, I think they can find their own<br>
machine configuration files.<br></blockquote><div><br></div><div>It is not about users being useful or "useless" as you claim. It is about getting the output I can pass to the editor right away as that would be the most common action anyway. Why would they need to find on their own when it can be returned right away? You do not like working more than needed, surely?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">>> By "machine configuration can be in the command line" do you mean<br>
>> MACHINE=foo? And if so, why does that mean the statement is vague?<br>
><br>
> Well, you could place a warning for instance when it is set to the same as<br>
> in the config file. That is probably not what the user intended.<br>
<br>
</div>I'm not sure what you meant here. Do you mean a situation where the<br>
local.conf says MACHINE=foo and the user also sets MACHINE=foo in the<br>
environment?<br></blockquote><div><br></div><div>Yes.</div></div></div></div>