On Mon, Oct 13, 2014 at 09:08:09AM -0300, Otavio Salvador wrote:
On Mon, Oct 13, 2014 at 5:53 AM, Tom Rini trini@ti.com wrote:
On Sun, Oct 12, 2014 at 05:48:37PM -0300, Otavio Salvador wrote:
The 'tools-only' target seems to be broken.
In a clean tree (no previous build) running:
$: make tools-only
fails with:
CHK include/config/uboot.release /bin/sh: 1: cannot open include/config/auto.conf: No such file Makefile:1049: recipe for target 'include/config/uboot.release' failed make: *** [include/config/uboot.release] Error 2
Any idea about the root cause? it is a regression as 2014.07 works fine in this case.
Well blah. The issue is that we support CONFIG_LOCALVERSION now and a few parts of "tools-only" use PLAIN_VERSION (some just for version printing but at least once for the DT in signed images). So a no-config tools-only build isn't posible again unless we want to ignore LOCALVERSION.
I would assume it to trigger:
make defconfig make silientoldconfig
by itself. So it could be used in old build recipes with no changes.
Here's what I can do. If you do sandbox_config and then tools-only and I take tools-only out of the "no config required" list (because it's not true!) it will work in both v2014.04 (when tools-only was introduced) and v2014.10.