"Burton, Ross" <ross.bur...@intel.com> writes: >> Is this check really so useful? gcc + g++ are elementary tools which can >> be expected. > > But they're not if BUILD_CC is overridden. For example if the host gcc is > actually too old/new for OE to work and BUILD_CC has been set to point at a > different compiler.
then, you will see a '<your-gcc>: command not found' very early in the build and every developer knows that '<your-gcc>' could not be found. When a misconfiguration is difficulty to detect or causes hidden breakage, sanity checks are important. But in this case, the check causes much more harm than it tries to solve (it will trigger e.g. for 'gcc -m32' too). Enrico -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core