All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: New recipes not installing in core-image-minimal
Date: Thu, 26 Jan 2012 17:57:11 -0800	[thread overview]
Message-ID: <4F220477.8030600@linux.intel.com> (raw)
In-Reply-To: <4F220105.3080600@linux.intel.com>



On 01/26/2012 05:42 PM, Saul Wold wrote:
> On 01/26/2012 05:29 PM, Darren Hart wrote:
>> In support of a new BSP I've written two new recipes and appended to
>> another to depend on them. The new recipes files are not appearing in
>> the resulting images. I'm sure I'm overlooking something trivial, but
>> I'm not sure what it would be. The layer is available here:
>>
>> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=dvhart/sys940x
>>
>> I've added ranpwd, genmac, and appended to netbase.
>>
>> netbase RDEPENDS on genmac and genmac RDEPENDS on ranpwd. Building
>> core-image-minimal triggers the build of genmac and ranpwd, and the
>> modified /etc/network/interfaces appears in the rootfs. genmac and
>> ranpwd place the appropriate files in their workdir/image directory, but
>> those files don't make it into the rootfs.
>>
> RDEPENDS_${PN} would work much better !

Perhaps, but it didn't fix this particular problem. Neither
/usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs. However,
each still appears in their respective workdir/image:

$ find
tmp/work/sys940x_noemgd-poky-linux/core-image-minimal-1.0-r0/rootfs
-name "ranpwd"
<NULL>

$ find
tmp/work/sys940x_noemgd-poky-linux/core-image-minimal-1.0-r0/rootfs
-name "genmac"
<NULL>

$ ls tmp/work/core2-poky-linux/genmac-1.0-r0/image/etc/init.d/
genmac

$ ls tmp/work/core2-poky-linux/ranpwd-git-r0/image/usr/bin/
ranpwd

genmac doesn't have a log.do_install in the workdir/temp directory. Is
that significant?

ranpwd does, but it isn't instructive:

$ cat tmp/work/core2-poky-linux/ranpwd-git-r0/temp/log.do_install
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common',
'common-linux', 'common-glibc', 'i586-linux', 'common']

Any other thoughts?


> 
> Sau!
> 
>> Can anyone offer an explanation as to why that might be? The top 4
>> commits of the repository linked to above will list the new recipes and
>> the bbappend for reference.
>>
>> Thanks,
>>

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-01-27  1:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27  1:29 New recipes not installing in core-image-minimal Darren Hart
2012-01-27  1:42 ` Saul Wold
2012-01-27  1:57   ` Darren Hart [this message]
2012-01-27  8:08     ` Martin Jansa
2012-01-27 10:22       ` Joshua Immanuel
2012-01-27 10:30         ` Martin Jansa
2012-01-27 17:13           ` Darren Hart
2012-01-30 11:02             ` Joshua Immanuel
2012-01-27  8:02 ` Martin Jansa
2012-01-27  8:06   ` Darren Hart
2012-01-31 18:21     ` Darren Hart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F220477.8030600@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=sgw@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.