Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake virtual/kernel -c menuconfig
Date: Tue, 02 Jun 2009 16:25:22 +0100	[thread overview]
Message-ID: <1243956322.2611.11.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <C62896630644CE43BF64B0FF0AC27F0E05B514@mail.ad.skymv.com>

On Tue, 2009-06-02 at 07:43 -0700, Chuck Kamas wrote:
> The kernel is 2.6.28 and the patches are the AT91 set.   What is
> interesting is that I change nothing but the distro= line and the
> menuconfig works with the patches applied.  I do know that there is a
> lot hidden behind the distro= line,  that is why I am asking the experts
> for their insight into how it all works and where to look for what is
> going wrong.

I just did "bitbake -c menuconfig
-b ../org.openembedded.dev/recipes/linux/linux_2.6.28.bb" using
DISTRO=minimal, MACHINE=at91sam9263ek and it seemed to apply the patches
correctly:

NOTE: Running task 4 of 5 (ID:
3, /home/pb/oe/org.openembedded.dev/recipes/linux/linux_2.6.28.bb,
do_patch)
NOTE: Applying patch
'linux-2.6.28-at91.patch' (tmp/work/at91sam9263ek-oe-linux-gnueabi/linux-2.6.28-r9/linux-2.6.28-at91.patch)
NOTE: Applying patch
'linux-2.6.28-exp.patch' (tmp/work/at91sam9263ek-oe-linux-gnueabi/linux-2.6.28-r9/linux-2.6.28-exp.patch)
NOTE: Running task 5 of 5 (ID:
4, /home/pb/oe/org.openembedded.dev/recipes/linux/linux_2.6.28.bb,
do_menuconfig)

So, I'm a bit baffled as to why it isn't working for you.  I also tried
the same thing with DISTRO=micro and, again, it worked fine for me.

> Regarding Angstrom:  I have no animosity against it. I am simply
> following the rule: "start with the bare metal and build up".

Right, that's a perfectly respectable point of view.  Micro, at least,
is less complicated than Angstrom and does have the potential to produce
smaller images.  Actually, that reminds me, I have some patches to
eliminate further bloat in micro that I should submit :-)

p.





  parent reply	other threads:[~2009-06-02 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 20:41 bitbake virtual/kernel -c menuconfig Chuck Kamas
2009-06-01 21:13 ` Koen Kooi
2009-06-02  5:18   ` Chuck Kamas
2009-06-02  7:54     ` Koen Kooi
2009-06-02 10:41     ` Philip Balister
2009-06-02  7:53 ` Phil Blundell
2009-06-02 14:43   ` Chuck Kamas
2009-06-02 15:23     ` Koen Kooi
2009-06-02 15:25     ` Phil Blundell [this message]
2009-06-02 17:05       ` Chuck Kamas
2009-06-02 17:46         ` Phil Blundell

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=1243956322.2611.11.camel@mill.internal.reciva.com \
    --to=pb@reciva.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox