From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
openembedded-core@lists.openembedded.org
Subject: Re: multilib errors
Date: Wed, 19 Sep 2012 14:31:39 +0100 [thread overview]
Message-ID: <3089732.XYZjcTqTr7@helios> (raw)
In-Reply-To: <CAMKF1srg0a1GhHPqY9dS_AjTJRXS7wSNzH1-UBMUJEuaXfuidw@mail.gmail.com>
On Wednesday 19 September 2012 06:26:31 Khem Raj wrote:
> On Wed, Sep 19, 2012 at 4:03 AM, Paul Eggleton
>
> <paul.eggleton@linux.intel.com> wrote:
> > I have seen these errors as well. It definitely should be doing these
> > checks - the warnings occur during the file checksum code but more
> > broadly they indicate the system will fail to find these files should you
> > try to build the targets mentioned. Looking more closely, I could be
> > wrong but it looks to me that BPN is not correct at least in the case of
> > lib64-build-appliance-image - I think it ought to be
> > "build-appliance-image" but instead it is "lib64-build-
> > appliance-image", which means that it can't find the files referred to in
> > SRC_URI anymore given that they are located in a directory named "build-
> > appliance-image".
>
> IMO when we inherit multilib bbclass then it should also add new
> ${BPN} based dirs to FILESPATH
BPN-based dirs are already in FILESPATH - that's the issue, BPN itself is not
the expected value.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-19 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 2:37 multilib errors McClintock Matthew-B29882
2012-09-19 11:03 ` Paul Eggleton
2012-09-19 13:26 ` Khem Raj
2012-09-19 13:31 ` Paul Eggleton [this message]
2012-09-19 13:37 ` Khem Raj
2012-09-19 19:53 ` McClintock Matthew-B29882
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=3089732.XYZjcTqTr7@helios \
--to=paul.eggleton@linux.intel.com \
--cc=B29882@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox