From: Tom Walsh <tom@openhardware.net>
To: openembedded-devel@lists.openembedded.org
Subject: do_rootfs fails
Date: Fri, 11 May 2007 13:45:47 -0400 [thread overview]
Message-ID: <4644ABCB.6080202@openhardware.net> (raw)
Ok, I admit it, I am totally confused by this whole "debian",
"multimachine", "package_ipk" stuff. I've been able to avoid
understanding this and think that this might be why bootstrap.image
won't build a filesystem image.
Prior to a month ago, I was using my own task + image bb files to build
my image. Since a lot of work has been done to make the task-base more
generic, I have moved my project over to using the stock
bootstrap-image.bb and task-base.bb files. However, it fails to build
properly.
When running a "bitbake bootstrap-image", everything builds but then
fails with:
========= begin ============
[tom@jtag oezipit]$ bitbake bootstrap-image
NOTE: Using cache in '/home/tom/oezipit/tmp/cache/zipit'
NOTE: Handling BitBake files: \ (4534/4534) [100 %]
NOTE: Parsing finished. 4329 cached, 0 parsed, 205 skipped, 0 masked.
NOTE: build 200705111324: started
OE Build Configuration:
BB_VERSION = "1.6.7"
OE_REVISION = "<unknown>"
TARGET_ARCH = "arm"
TARGET_OS = "linux"
MACHINE = "zipit"
DISTRO = "zipit"
DISTRO_VERSION = "1.0"
TARGET_FPU = "soft"
NOTE: multiple providers are available (db3, db);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db
NOTE: multiple providers are available (db3-native, db-native);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db-native
NOTE: package bootstrap-image-1.0: started
NOTE: package bootstrap-image-1.0-r0: task do_rootfs: started
ERROR: function do_rootfs failed
ERROR: see log in
/home/tom/oezipit/tmp/work/zipit-linux/bootstrap-image-1.0-r0/temp/log.do_rootfs.17150
NOTE: Task failed:
/home/tom/oezipit/tmp/work/zipit-linux/bootstrap-image-1.0-r0/temp/log.do_rootfs.17150
NOTE: package bootstrap-image-1.0-r0: task do_rootfs: failed
ERROR: TaskFailed event exception, aborting
NOTE: package bootstrap-image-1.0: failed
ERROR: Build of bootstrap-image failed
========= snip =============
When I check the logfile, it says that "sh: fakeroot: command not
found". This is correct, fakeroot-native has NOT been built. So, I do
a "bitbake -c rebuild fakeroot-native", then run "bitbake
bootstrap-image" again.
It then fails with a logfile message of
"/home/tom/oezipit/tmp/work/zipit-linux/bootstrap-image-1.0-r0/temp/run.do_rootfs.24175:
line 312: ipkg-cl: command not found". Again, this is true, ipkg-native
is not present. So, I do a "bitbake -c rebuild ipkg-native", then run
"bitbake bootstrap-image" again.
Now it builds the filesystem target tarball image.
How can I automate those needs for fakeroot-native and ipkg-native? I'm
not sure where to look, this was working a few weeks ago.
Regards,
TomW
--
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net http://cyberiansoftware.com http://openzipit.org
"Windows? No thanks, I have work to do..."
----------------------------------------------------
next reply other threads:[~2007-05-11 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 17:45 Tom Walsh [this message]
2007-05-11 18:07 ` do_rootfs fails Koen Kooi
2007-05-11 18:24 ` Michael Krelin
2007-05-12 21:33 ` Stelios Koroneos
2007-05-19 17:50 ` Richard Purdie
2007-05-12 0:07 ` Matthias Hentges
2007-05-12 10:28 ` Koen Kooi
2007-05-14 12:42 ` Richard Purdie
2007-05-14 22:23 ` Matthias Hentges
-- strict thread matches above, loose matches on Subject: below --
2012-07-31 10:37 Andreas Müller
2012-07-31 10:42 ` Martin Jansa
2012-07-31 11:01 ` Andreas Müller
2012-07-31 11:21 ` Paul Eggleton
2012-07-31 11:34 ` Paul Eggleton
2013-04-09 8:07 Jaap de Jong
2013-04-09 11:37 ` Jaap de Jong
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=4644ABCB.6080202@openhardware.net \
--to=tom@openhardware.net \
--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.