On 1/12/17 3:42 PM, Richard Purdie wrote: > On Thu, 2017-01-12 at 11:24 -0800, Juro Bystricky wrote: >> When a non-existing MACHINE is specified, sanity check issues >> the following message: >> >> Please set a valid MACHINE in your local.conf or environment >> >> However, MACHINE can also be set in multiconfig .conf file(s). >> Hence we may have several different MACHINE settings within one >> (multiconfig) build, so the present error message is fairly >> ambiguous. >> >> This patch remedies this by explicitly naming the offending MACHINE >> and >> adding conf/multiconfig/*.conf to the list of places where this >> erroneous >> MACHINE definition could have originated. >> >> Invalid MACHINE=xyz. Please set a valid MACHINE in your >> local.conf, conf/multiconfig/*.conf or environment > > Can we change this to: > > "MACHINE=xyz is invalid. Please set a valid MACHINE in your local.conf, > environment or other configuration file."
I commented elsewhere as well -- but is there any way to see where MACHINE was actually set and display that -- or is it limited to 'bitbake -e' usage? --Mark > I don't want to have to list all the possible places you could set > MACHINE. > > Cheers, > > Richard > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
