From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2A7C6E0144E for ; Thu, 15 Aug 2013 12:47:17 -0700 (PDT) Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga102.ch.intel.com with ESMTP; 15 Aug 2013 12:47:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,887,1367996400"; d="scan'208";a="282541722" Received: from unknown (HELO [10.255.14.106]) ([10.255.14.106]) by AZSMGA002.ch.intel.com with ESMTP; 15 Aug 2013 12:47:16 -0700 Message-ID: <520D3044.6000904@linux.intel.com> Date: Thu, 15 Aug 2013 12:47:16 -0700 From: Saul Wold User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: "Paul D. DeRocco" References: <520D242A.6040103@linux.intel.com> In-Reply-To: Cc: yocto@yoctoproject.org Subject: Re: My stuff is missing from rootfs X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Aug 2013 19:47:21 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 08/15/2013 12:30 PM, Paul D. DeRocco wrote: >> From: Saul Wold >> >>> On 08/15/2013 11:37 AM, Paul D. DeRocco wrote: >>> I've done exactly this in a different Yocto-based project, >>> and it worked. >>> Now I'm trying to do the same thing in a Gumstix build, and it's not >>> working. I have a dumb little recipe that merely copies >>> some files into >>> particlar places in the rootfs. It adds a systemd service >>> unit, as well as >>> .bashrc and .inputrc to /home/root. >>> >>> The build logs show the recipe being processed, including >>> the do_install >>> task which copies the files. No errors are produced. If I >>> rummage through >>> build/tmp/work, I can find the fragment of the rootfs containing the >>> /home/root and /etc/systemd/system directories with my >>> files in them. Yet no >>> matter what I try, these things never wind up in the final rootfs. >>> >>> I've tried clean and cleansstate on the recipe, as well as >>> on my top-level >>> recipe. I've bumped PR from r0 to r1. It dutifully >>> reprocesses my recipe, >>> with no errors, and I end up with a perfectly functioning >>> rootfs without >>> these particular files. >>> >>> This is a slightly modified version of >>> gumstix-console-image. I believe it's >>> based on Danny, as the gumstix Dylan stuff is still a work >>> in progress. >>> >>> What could conceivably be wrong? >>> >> Where do you add your recipe's generated packages to the image, this >> could be in your custom image with an RDEPENDS or via something in >> local.conf like CORE_IMAGE_EXTRA_INSTALL_append = " ". >> >> Do you have other recipes that DEPEND or RDEPEND on your recipe? >> >> That might point you in the right direction. > > My top level recipe uses IMAGE_INSTALL to add a bunch of packages, including > one whose name matches the name of the recipe that's being processed but > whose output is being ignored. This is exactly what I did in a different > Yocto project, to get a similar recipe to install some similar files, and it > all worked fine. > > I've attached the top level recipe and the problematic one, only changing > the project name to "foo" for proprietary reasons. > Interesting, did you verify that the files are in the tmp/work/.../foo/packages-split/foo directory. You can also look in the tmp/work/.../gumstix-foo-pyygtk-image/1.0-r0/installed_pkgs.txt file to ensure your foo package is there. You can also look in the image temp dir for the log.do_rootfs and see if there are any issues in it or it's missing your package. Note in this case recipename == packagename, this is not always the case. Home this helps. Sau!