From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: sstate breakage with multimachine
Date: Tue, 17 May 2011 10:37:02 +0100 [thread overview]
Message-ID: <1305625022.3424.210.camel@rex> (raw)
In-Reply-To: <E79027E3-2F0B-40DF-8798-6AF5D6C3E4E8@dominion.thruhere.net>
On Tue, 2011-05-17 at 08:34 +0200, Koen Kooi wrote:
> Thanks for looking into this! For the time being I'll work around it with:
>
> oen@dominion:/OE/tentacle/sources/meta-angstrom$ git diff conf/distro/
> diff --git a/conf/distro/include/angstrom-core-tweaks.inc b/conf/distro/include/angstrom-core-tweaks.inc
> index e4bd798..fe9225c 100644
> --- a/conf/distro/include/angstrom-core-tweaks.inc
> +++ b/conf/distro/include/angstrom-core-tweaks.inc
> @@ -18,6 +18,11 @@ STAGING_DIR_HOST = "${STAGING_DIR}/${MACHINE}-${TCLIBC}"
> +# Work around multimachine breakage
> +# See http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/002535.html
> +
> +LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses"
>
> I think that's a better place to stash those licenses, since we drop images in DEPLOY/image, sources in DEPLOY/sources and sdks in DEPLOY/sdk so DEPLOY/licenses makes sense.
>
> Do you want me to send a patch to license.bbclass for this?
Yes please.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-17 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 11:20 sstate breakage with multimachine Koen Kooi
2011-05-16 23:13 ` Richard Purdie
2011-05-17 6:34 ` Koen Kooi
2011-05-17 9:37 ` Richard Purdie [this message]
2011-05-17 7:14 ` Martin Jansa
2011-05-17 9:42 ` Richard Purdie
2011-05-17 11:37 ` Martin Jansa
2011-05-17 23:10 ` Richard Purdie
2011-05-18 4:26 ` Martin Jansa
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=1305625022.3424.210.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox