Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: RaNgErS <rangers.av@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Kernal build errors
Date: Mon, 29 Oct 2012 11:57:56 +0000	[thread overview]
Message-ID: <8894147.TkBjTbKHcp@helios> (raw)
In-Reply-To: <CAMQ5J2bC+3514kz1sNsqL_zb10P5rdnsCy_Xd2Z9-Gm1-WdTSg@mail.gmail.com>

On Monday 29 October 2012 16:49:59 RaNgErS wrote:
> could you please explain how should i check the kernel configuration?

There will probably be a defconfig for your kernel somewhere, in a directory 
next to the kernel recipe.

> and changing RRECOMMENDS to RDEPENDS

Have a look at the recipe (I guess recipes/tasks/task-picop-demo.bb), you will 
see some lines that use RDEPENDS to bring in the kernel modules.

Cheers,
Paul

PS: please CC the mailing list on reply, thanks.

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2012-10-29 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMQ5J2a8zLVVDPNw6vHhgsQ1pRhz_QdqaJJz7U_aQv2MwEg5zQ@mail.gmail.com>
2012-10-29  7:51 ` Kernal build errors RaNgErS
2012-10-29  9:43   ` Paul Eggleton
     [not found]     ` <CAMQ5J2bC+3514kz1sNsqL_zb10P5rdnsCy_Xd2Z9-Gm1-WdTSg@mail.gmail.com>
2012-10-29 11:57       ` Paul Eggleton [this message]
2012-10-30  7:29         ` RaNgErS
2012-10-30  8:54     ` Koen Kooi
2012-10-31  4:04       ` RaNgErS
     [not found] <mailman.12599.1349694752.14518.openembedded-devel@lists.openembedded.org>
     [not found] ` <CAMQ5J2b9V6eTXO5ZirYWyDkQeCXg4Mz-+LK+Zq+sunXHaawF1A@mail.gmail.com>
     [not found]   ` <CAMQ5J2YGecs27ETGVeOgJrQV_UqfpLf+qU0Jnx=SAcj493njZg@mail.gmail.com>
2012-10-23  7:33     ` RaNgErS

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=8894147.TkBjTbKHcp@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rangers.av@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox