From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1.windriver.com ([147.11.146.13]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1URpco-0002wQ-8f for openembedded-core@lists.openembedded.org; Mon, 15 Apr 2013 22:03:45 +0200 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r3FJk6ht000775 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Apr 2013 12:46:06 -0700 (PDT) Received: from yow-bashfiel-d3.wrs.com (128.224.147.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.2.342.3; Mon, 15 Apr 2013 12:46:06 -0700 From: Bruce Ashfield To: Date: Mon, 15 Apr 2013 12:45:55 -0700 Message-ID: X-Mailer: git-send-email 1.7.10.4 MIME-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: [PATCH 0/1] kern-tools: fix custom repository BSP generation X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 20:03:51 -0000 Content-Type: text/plain Richard, As was reported on the oe-core mailing list earlier today, custom BSPs (other than the ones generated by the BSP tooling) that relied on generated BSP descriptions started failing. I did the following one line patch to fix them. Updating the SCRCREV to pick up the following fix updateme: use absolute path for generated BSP descriptions When a custom BSP is used, a top level BSP is generated by the tools and fed to the build system just as a user defined BSP would be located and passed. The location of the generated file is placed in the top_tgt file, which is used by subsequent stages. A relative path was being placed into top_tgt, which binds the build to a particular directory structure and working directory. The location of parts of the build have changed, and this relative path is no longer accurate. Changing it to an absolute path solve the build issues related to custom BSPs. There's no risk to existing kernels, or built binary images. The only thing that runs this code is BSP generation routines that are triggered by linux-yocto-custom. If there's any room in 1.4, this one-line would be a good idea! Cheers, Bruce The following changes since commit 45c8cc1a58e7868f4603be08a86fef178edfc926: poky.conf: add Poky 1.4 and CentOS 6.4 to SANITY_TESTED_DISTROS (2013-04-15 17:21:28 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): kern-tools: fix custom repository BSP generation meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 1.7.10.4