From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] ghostscript: fix parallel make issue
Date: Thu, 29 Mar 2012 22:29:09 +0100 [thread overview]
Message-ID: <1333056549.18082.32.camel@ted> (raw)
In-Reply-To: <a913503c671f8442d554a5f54cf93bcf8219a53d.1332927487.git.kai.kang@windriver.com>
On Wed, 2012-03-28 at 17:41 +0800, Kang Kai wrote:
> [Yocto 1202]
>
> Update ghostscript-9.02-parallel-make.patch to fix parallel make
> failure.
> Bump up PR.
>
> Signed-off-by: Kang Kai <kai.kang@windriver.com>
> ---
> .../ghostscript-9.02-parallel-make.patch | 13 +++++++++++++
> .../ghostscript/ghostscript_9.05.bb | 2 +-
> 2 files changed, 14 insertions(+), 1 deletions(-)
Sadly the makefiles are littered with CP_ races. I've merged a patch
which hopefully addresses them all rather than fixing them up one by one
as they occur.
Cheers,
Richard
prev parent reply other threads:[~2012-03-29 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:41 [PATCH 0/1] ghostscript: work around for parallel build issue Kang Kai
2012-03-28 9:41 ` [PATCH 1/1] ghostscript: fix parallel make issue Kang Kai
2012-03-29 21:29 ` Richard Purdie [this message]
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=1333056549.18082.32.camel@ted \
--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