From: Kang Kai <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] ghostscript: work around for parallel build issue
Date: Wed, 28 Mar 2012 17:41:44 +0800 [thread overview]
Message-ID: <cover.1332927487.git.kai.kang@windriver.com> (raw)
Hi,
The patch is for Yocto 1202, to fix parallel build issue.
Test it 100 times for mips and 4 times show the error mesage that "Files exists"
but bitbake compile pass.
Regards,
The following changes since commit 7b01671f54f70c28c98457058c51ffefcb07c0e8:
nspr 4.8.9: failed to build on x86_64 board (2012-03-27 13:26:37 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/fix-gs
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/fix-gs
Kang Kai (1):
ghostscript: fix parallel make issue
.../ghostscript-9.02-parallel-make.patch | 13 +++++++++++++
.../ghostscript/ghostscript_9.05.bb | 2 +-
2 files changed, 14 insertions(+), 1 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-03-28 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:41 Kang Kai [this message]
2012-03-28 9:41 ` [PATCH 1/1] ghostscript: fix parallel make issue Kang Kai
2012-03-29 21:29 ` 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=cover.1332927487.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--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