From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] seperatebuilddir.inc: disable seperate build dir for consolekit
Date: Tue, 16 Apr 2013 16:53:47 +0100 [thread overview]
Message-ID: <1366127627.8670.98.camel@ted> (raw)
In-Reply-To: <1366112971-3644-1-git-send-email-koen@dominion.thruhere.net>
On Tue, 2013-04-16 at 13:49 +0200, Koen Kooi wrote:
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/conf/distro/include/seperatebuilddir.inc | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/conf/distro/include/seperatebuilddir.inc b/meta/conf/distro/include/seperatebuilddir.inc
> index a9ca240..f60dc5c 100644
> --- a/meta/conf/distro/include/seperatebuilddir.inc
> +++ b/meta/conf/distro/include/seperatebuilddir.inc
> @@ -78,7 +78,9 @@ B_pn-compositeproto = "${SEPB}"
> B_pn-compositeproto-native = "${SEPB}"
> #B_pn-connman = "${SEPB}"
> #B_pn-connman-gnome = "${SEPB}"
> -B_pn-consolekit = "${SEPB}"
> +#B_pn-consolekit = "${SEPB}"
> +#| /build/setup-scripts/build/tmp-angstrom_next-eglibc/work/cortexa8hf-vfp-neon-angstrom-linux-gnueabi/consolekit/0.4.5-r10/ConsoleKit-0.4.5/pam-ck-connector/pam-ck-connector.c:64:26: fatal error: ck-connector.h: No such file or directory
> +#| compilation terminated.
> B_pn-console-tools = "${SEPB}"
> B_pn-coreutils = "${SEPB}"
> B_pn-coreutils-native = "${SEPB}"
Neither my local builds or the autobuilder see this. Any idea why some
builds would fail and others would work?
Cheers,
Richard
next prev parent reply other threads:[~2013-04-16 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:49 [PATCH] seperatebuilddir.inc: disable seperate build dir for consolekit Koen Kooi
2013-04-16 15:53 ` Richard Purdie [this message]
2013-04-16 16:29 ` Koen Kooi
2013-04-16 21:08 ` Richard Purdie
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=1366127627.8670.98.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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