From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] libcgroup_0.37.1.bb: Add recipe
Date: Mon, 23 Jul 2012 11:00:31 +0100 [thread overview]
Message-ID: <4960258.KFiZKWHEoN@helios> (raw)
In-Reply-To: <1343001258-19551-3-git-send-email-raj.khem@gmail.com>
On Sunday 22 July 2012 16:54:18 Khem Raj wrote:
> +# We really need the symlink so :(
> +ERROR_QA = "debug-deps dev-deps debug-files arch la2 pkgconfig la perms"
Why do you need this? If you really do need it, you must use INSANE_SKIP and
not ERROR_QA here.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-23 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 23:54 [PATCH 1/3] qemu.bbclass: Map the qemu binary name for powerpc64 Khem Raj
2012-07-22 23:54 ` [PATCH 2/3] cups_1.4.6.bb: Fix build on ppc64 Khem Raj
2012-07-22 23:54 ` [PATCH 3/3] libcgroup_0.37.1.bb: Add recipe Khem Raj
2012-07-23 10:00 ` Paul Eggleton [this message]
2012-07-26 19:26 ` [PATCH 1/3] qemu.bbclass: Map the qemu binary name for powerpc64 Saul Wold
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=4960258.KFiZKWHEoN@helios \
--to=paul.eggleton@linux.intel.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