From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building a rootfs, without building a kernel
Date: Tue, 24 Jun 2008 17:01:44 -0400 [thread overview]
Message-ID: <486160B8.2050400@balister.org> (raw)
In-Reply-To: <g3rkne$jbo$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Koen Kooi wrote:
> Philip Balister wrote:
>> I am trying to build a powerpc root file system for a xilinx ml403
>> board. Since we do not have a working kernel build for this machine, I
>> tried commenting out the PREFERRED_PROVIDER for virtual/linux. The build
>> then tries to build linux-rt. I tried ASSUME_PROVIDED for the kernel
>> when the preferred provider is not commented out and it still tries to
>> build the kernel.
>>
>> Looking at the dependency graphs seems to suggest the requirement comes
>> from the do_rootfs task.
>>
>> Does anyone know how to build an image, without building a kernel for a
>> machine?
>
> bitbake -b foo-image.bb is what I use, since I'm lazy ;)
Sadly, this does not build all the dependencies needed for the image and
I am really lazy.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-06-24 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 20:04 Building a rootfs, without building a kernel Philip Balister
2008-06-24 20:16 ` Koen Kooi
2008-06-24 21:01 ` Philip Balister [this message]
2008-06-26 12:03 ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-06-29 22:29 ` Michael 'Mickey' Lauer
2008-06-29 23:08 ` David Baird
2008-07-01 18:14 ` Philip Balister
2008-07-02 7:36 ` Ben Lau
2008-07-03 15:03 ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-07-03 17:20 ` Philip Balister
2008-07-04 13:59 ` Rodrigo Vivi
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=486160B8.2050400@balister.org \
--to=philip@balister.org \
--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 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.