From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-initramfs][PATCH] klcc_cross: move in target sysroot as crosscript
Date: Fri, 02 May 2014 09:38:10 +0100 [thread overview]
Message-ID: <1399019890.12731.28.camel@ted> (raw)
In-Reply-To: <CAAQYJAtY33YvGL7RVYpBiKtOkt3OxV7h=XV0EyY8yovZwDFdtg@mail.gmail.com>
On Fri, 2014-05-02 at 10:34 +0200, Andrea Adami wrote:
> I probably misunderstand that part.
>
> I could not see any difference in the produced klcc.cross scripts with
> or without the mangling.
> Tested runtime on 3 machines.
> What I did not yet try is a rebuild from sstate but I expect it to be rebuilt.
The easy way to reproduce a problem is to build for MACHINE=A and then
build for MACHINE=B where the two machines have the same architecture.
You will find that whilst it will switch the commented line at the top
to refer to the new machine, the encoded lines do not get changed.
You would also find that if you run a build in dirA, then a build in
dirB using the sstate cache from dirA, the paths would reference dirA,
not dirB. After this change they will reference dirB.
Cheers,
Richard
next prev parent reply other threads:[~2014-05-02 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 23:13 [meta-initramfs][PATCH] klcc_cross: move in target sysroot as crosscript Andrea Adami
2014-05-01 23:13 ` [meta-initramfs][PATCH] kexecboot: fix build when S != B Andrea Adami
2014-05-02 8:21 ` [meta-initramfs][PATCH] klcc_cross: move in target sysroot as crosscript Richard Purdie
2014-05-02 8:34 ` Andrea Adami
2014-05-02 8:38 ` Richard Purdie [this message]
2014-05-02 8:45 ` Andrea Adami
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=1399019890.12731.28.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=andrea.adami@gmail.com \
--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.