From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Thu, 20 Nov 2014 11:55:48 -0800 Subject: [U-Boot] help on using buildman In-Reply-To: References: <546E3731.6080006@freescale.com> <546E3F77.9010503@freescale.com> <546E4504.5040906@freescale.com> Message-ID: <546E4744.3090108@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/20/2014 11:51 AM, Simon Glass wrote: >> >> Nothing more than that. Where shall I look for ARCH? > > That doesn't look like a full build to me. The 'err' file may have > more clues. You could try without '--force-build --force-reconfig' > perhaps. > No, it failed. The err file has this $ cat err make[1]: *** No rule to make target `../arch//cpu/u-boot.lds', needed by `u-boot.lds'. Stop. make[1]: *** Waiting for unfinished jobs.... make: *** [sub-make] Error 2 >> >> If I build for board T4240QDS, it has error on most but not all. T4240QDS >> T4240QDS_SRIO_PCIE_BOOT T4240QDS_SECURE_BOOT failed, but T4240QDS_NAND didn't. > > It's a bit of a mystery. How about adding V=1 in your make flags in ~/.buildman: > I think the key is to configure it, not build it. With the failure case, it doesn't build. I am thinking to find the equivalent to "make ARCH=power ...". How to dump that? York