On Thu, Aug 1, 2013 at 11:56 AM, Burton, Ross <[email protected]> wrote:
> On 1 August 2013 11:50, Laszlo Papp <[email protected]> wrote: > > Speaking of gerrit terms: I would prefer that you didn't submit this. > > > > I would like it to be more specific. If it cannot be more specific, it > > should provide further information to get more specific information. > Note, > > machine configuration can be the command line as well, so this would > still > > be vague. > > It cannot be more specific without dumping the entire machine > configuration, which won't help because a variable is *not* set. > No no, it could print out the concrete file to look up, not just a name. Besides, I would probably even print a warning about the entry point and load address not set. > By "machine configuration can be in the command line" do you mean > MACHINE=foo? And if so, why does that mean the statement is vague? > Well, you could place a warning for instance when it is set to the same as in the config file. That is probably not what the user intended.
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
