From: scerveau <scerveau@gmail.com>
To: yocto@yoctoproject.org
Subject: [dizzy branch] License list fails with rpm with package shared between two arch
Date: Wed, 4 Nov 2015 11:02:50 +0100 [thread overview]
Message-ID: <5639D7CA.7080404@gmail.com> (raw)
Dear all,
I'm having a machine A and a machine B.
This two machines are built against the same image class and in the same
build folder.
But on machine A there is a recipe LAMBDA which is not include in
machine B.
The package LAMBDA is shared in the same folder
cortexa9hf_vfp_neon....(Machine A and B use the same imx arch)
If i build machine A(everything is ok) and then machine B, during the
last recipe execution image rootfs of machine B, a list of package is
performed to build the license list with this missing package which
finally fails saying that license folder does not exist. I guess the rpm
package list performed in poky/lib/oe/package_manager.py is not correct
and should be done according to the image instead of the list of files
in the folder cortexa9hf_vfp_neon.
I found a hack by putting my recipe LAMBDA dependent to my machine so
the package is not in cortexa9hf_vfp_neon anymore.
If someone could help me on this issue, it would be very nice because i
guess there is something wrong in yocto base tools.
BR.
Stephane
reply other threads:[~2015-11-04 10:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5639D7CA.7080404@gmail.com \
--to=scerveau@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.