From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: image.bbclass broken?
Date: Mon, 16 Feb 2009 03:26:07 -0500 [thread overview]
Message-ID: <20090216082607.GA30105@denix.org> (raw)
In-Reply-To: <000d01c98f79$3e36e6d0$baa4b470$@com>
On Sun, Feb 15, 2009 at 03:25:24PM +0100, Christian P?ssinger wrote:
> Hello,
>
> after a recent 'git pull' of the -dev branch I'm not able to create images.
>
> I receive the following error:
>
> | awk: {size = 10240 + $1; print (size > ${IMAGE_ROOTFS_SIZE} ? size :
> ${IMAGE_ROOTFS_SIZE}) }
> | awk:
> ^ syntax
> | du: write error
>
> Doing a grep for the line I found it:
>
> org.openembedded.dev/classes/image.bbclass:110:
> ROOTFS_SIZE=`du -ks ${IMAGE_ROOTFS}|awk '{size = ${IMAGE_EXTRA_SPACE} + $1;
> print (size > ${IMAGE_ROOTFS_SIZE} ? size :
> ${IMAGE_ROOTFS_SIZE}) }'`
>
> After replacing image.bbclass with the one from the -stable branch
> everything worked again. I run OE on an up-2-date Ubuntu Server 8.10.
>
> Can anyone confirm this behavior?
Christian,
The change was made almost a month ago:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=d38f1dd24dd6ed94408aa49aad33e46634a129ff
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=9d7586e655755f51be3f09f3da48147b0937c3e1
I haven't heard of anyone having any issues creating images since then.
Now, judging from the error message, I'd guess you have IMAGE_ROOTFS_SIZE
variable undefined. Normally it is set to a default value by conf/bitbake.conf,
unless it was specifically set in one of the image recipes and/or your
local.conf...
--
Denys
prev parent reply other threads:[~2009-02-16 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 14:25 image.bbclass broken? Christian Pössinger
2009-02-16 8:26 ` Denys Dmytriyenko [this message]
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=20090216082607.GA30105@denix.org \
--to=denis@denix.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.