From: Mark Hatle <mark.hatle@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, "Khor, Boon Pin" <boon.pin.khor@intel.com>
Subject: Re: Yocto Project 1.2 Beta testing instructions
Date: Tue, 10 Apr 2012 12:21:50 -0500 [thread overview]
Message-ID: <4F846C2E.8040304@windriver.com> (raw)
In-Reply-To: <2083054.YjdMd9bIMH@helios>
On 4/10/12 4:18 AM, Paul Eggleton wrote:
> On Wednesday 04 April 2012 18:08:58 Liu, Song wrote:
>> Can someone help answer the following question? This happens during Boon
>> Pin's beta testing using the build at:
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/snapshot/poky-8e9f6fc77ac476
>> 3f4ed1f6e7b720420c220ba6e2.tar.bz2 .
>> ...
>> | Processing task-core-boot...
>> | Manifest:
>> | /home/nemo/yp-beta-build/tmp/work/qemux86-poky-linux/core-image-minimal-1
>> | .0-r0/rootfs/install/install.manifest local: 1: -Uhv: bad variable name
>>
>> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
>> ERROR: Task 8
>> (/home/nemo/yp-beta/meta/recipes-core/images/core-image-minimal.bb,
>> do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1329
>> tasks of which 287 didn't need to be rerun and 1 failed.
>
> Sorry for the late reply, presumably this issue is still present?
>
>> Maybe I am missing rpm packages in ubuntu ?
>
> You don't need to install rpm on the host system, we build rpm-native for
> that.
>
> Mark, any clues what could be going wrong here?
I've never seen any problem like this before. Below is some analysis and a
question at the very end...
There are only two places in the system where the string -Uhv exists:
package_rpm.bbclass:
rpm_common_comand --replacepkgs \
-Uhv ${target_rootfs}/install/total_solution.manifest
(rpm_common_comand is a shell function it appears... the arguments to the
function are passed, via $@ to an RPM command)
rootfs_rpm.bbclass:
rootfs_install_packages() {
# The pkg to be installed here is not controlled by the
# package_install_internal_rpm, so it may have already been
# installed(e.g, installed in the first time when generate the
# rootfs), use '--replacepkgs' to always install them
for pkg in $@; do
${RPM} --root ${IMAGE_ROOTFS} -D "_dbpath ${rpmlibdir}" \
-D "__dbi_txn create nofsync private" \
--noscripts --notriggers --noparentdirs --nolinktos \
--replacepkgs -Uhv $pkg || true
done
}
I would guess from the error that it's the one in package_rpm.bbclass that
failed.. if that is the case, then all I can think of is what shell? Are we
using a bash-ism? Does "dash" on ubuntu have shell functions enabled in it, if
not that might be the problem.
Please check your system's /bin/sh.. is it a symlink, if so, what does it point
to? If it points to "dash", change it to "bash" and see if the error still occurs.
--Mark
next prev parent reply other threads:[~2012-04-10 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7E680CB2A76BB8438D08CF13C09FC53A46AE31E3@ORSMSX101.amr.corp.intel.com>
[not found] ` <F9AC6E797E022941A4CD80AAEDFAD67D43756F@PGSMSX103.gar.corp.intel.com>
2012-04-04 18:08 ` Yocto Project 1.2 Beta testing instructions Liu, Song
2012-04-10 9:18 ` Paul Eggleton
2012-04-10 17:21 ` Mark Hatle [this message]
2012-04-10 23:06 ` Khor, Boon Pin
2012-04-10 23:39 ` Mark Hatle
2012-04-10 23:57 ` Khor, Boon Pin
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=4F846C2E.8040304@windriver.com \
--to=mark.hatle@windriver.com \
--cc=boon.pin.khor@intel.com \
--cc=paul.eggleton@linux.intel.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.