From: Trevor Woerner <twoerner@gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] du giving non-integer result?
Date: Thu, 10 Sep 2015 21:37:15 -0400 [thread overview]
Message-ID: <55F2304B.6070601@gmail.com> (raw)
In-Reply-To: <55ECF934.80902@gmail.com>
From the feedback, it looks like I'm the only one seeing this issue.
That's okay, but I'll update this issue with new information in case
it's useful to others. Today I also had some other strangeness with the
"make sd card image" portion of a build, this time for cubietruck
(meta-sunxi):
ERROR: Error: The image creation script
'/z/tmp/build/tmp/work/cubietruck-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.sunxi-sdimg'
returned 1:
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.0606e-05 s, 0.0 kB/s
expr: non-integer argument
WARNING:
/z/tmp/build/tmp/work/cubietruck-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.sunxi-sdimg:1
exit 1 from
parted -s
/z/tmp/build/tmp/deploy/images/cubietruck/core-image-minimal-cubietruck-20150910182624.rootfs.sunxi-sdimg
unit KiB mkpart primary ext2 $(expr ${BOOT_SPACE_ALIGNED} \+ 2048)
$(expr ${BOOT_SPACE_ALIGNED} \+ 2048 \+ 10240.0)
Not only am I getting the floating point again, but it looks like
"BOOT_SPACE_ALIGNED" isn't getting expanded!
The frustrating part is that simply rerunning "bitbake
core-image-minimal" fixes the problem. The second time it completes
without error.
next prev parent reply other threads:[~2015-09-11 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 2:40 [meta-raspberrypi] du giving non-integer result? Trevor Woerner
2015-09-07 7:21 ` Khem Raj
2015-09-07 7:40 ` Trevor Woerner
2015-09-08 5:56 ` Michael Fainstein
2015-09-25 14:12 ` Dave Wolaver
2015-09-25 15:00 ` Daniel.
2015-09-11 1:37 ` Trevor Woerner [this message]
2015-09-17 4:14 ` Jonathan Liu
2015-09-23 20:12 ` Andrei Gherzan
2015-09-24 0:44 ` Trevor Woerner
2015-09-24 7:36 ` Colin Helliwell
2015-10-21 12:14 ` Andrei Gherzan
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=55F2304B.6070601@gmail.com \
--to=twoerner@gmail.com \
--cc=yocto@yoctoproject.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.