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 09:43:02 +0000 [thread overview]
Message-ID: <1514371.ACA88Gs2zU@helios> (raw)
In-Reply-To: <CAMQ5J2aXaBZg3k3Guj=B+KgdKnf_Px3OmKu8C5oKmyiwdG7AFw@mail.gmail.com>
On Monday 29 October 2012 13:21:50 RaNgErS wrote:
> I am very new to this stuff, and I tried to build an image i got some
> errors which are not solved even i tried for a whole week. It is from the
> kernal side or sth. i am attaching the log file obtained .
The module packages specified don't exist, which means either the functionality
they would have included is compiled into the kernel (option value = "y") or
they weren't enabled at all (option value="n"). So you should check your
kernel configuration.
If they are enabled but you do genuinely want these to be compiled into the
kernel rather than as modules, the task-picop-demo recipe needs to be changed
to use RRECOMMENDS rather than RDEPENDS to bring in the kernel modules only if
they exist; that will fix the error.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-29 9:56 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 [this message]
[not found] ` <CAMQ5J2bC+3514kz1sNsqL_zb10P5rdnsCy_Xd2Z9-Gm1-WdTSg@mail.gmail.com>
2012-10-29 11:57 ` Paul Eggleton
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=1514371.ACA88Gs2zU@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 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.