From: Kang Kai <kai.kang@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: [PATCH 0/1]ghostscript: add patches to make it run cross compile platform V2
Date: Sat, 21 May 2011 16:24:37 +0800 [thread overview]
Message-ID: <cover.1305963432.git.kai.kang@windriver.com> (raw)
From: Kang Kai <kai.kang@windriver.com>
Hi Richard,
I update the patches with your opinion, thanks!
When test lsb on ppc find that gs can't run. The root cause is gs determines some target configuration
on build system. According to the document of ghostscript,
http://pages.cs.wisc.edu/~ghost/doc/cvs/Make.htm#Cross-compiling
when cross compile ghostscript need some manual work.
So import patches from WindRiver Linux to make sure ghostscript can be cross compiled, and spit the patches
into arch/[so]obj.h source files.
The following changes since commit 7706d5d844db2725f4118207d90e302679eacdfe:
linux-yocto/meta-yocto: fix gcc 4.6.0 compilation failures (2011-05-19 17:33:50 -0700)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib.git kangkai/distro
http://git.pokylinux.org/cgit.cgi//log/?h=kangkai/distro
Kang Kai (1):
ghostscript: fix run failure on mpc8315e
meta/recipes-extended/ghostscript/arm/objarch.h | 40 +++++++++++++++++++
meta/recipes-extended/ghostscript/arm/soobjarch.h | 40 +++++++++++++++++++
.../ghostscript/ghostscript-9.02-genarch.patch | 27 +++++++++++++
.../ghostscript/ghostscript_9.02.bb | 22 +++++++++-
meta/recipes-extended/ghostscript/i586/objarch.h | 41 ++++++++++++++++++++
meta/recipes-extended/ghostscript/i586/soobjarch.h | 41 ++++++++++++++++++++
meta/recipes-extended/ghostscript/mips/objarch.h | 40 +++++++++++++++++++
meta/recipes-extended/ghostscript/mips/soobjarch.h | 40 +++++++++++++++++++
.../recipes-extended/ghostscript/powerpc/objarch.h | 40 +++++++++++++++++++
.../ghostscript/powerpc/soobjarch.h | 40 +++++++++++++++++++
meta/recipes-extended/ghostscript/x86_64/objarch.h | 40 +++++++++++++++++++
.../ghostscript/x86_64/soobjarch.h | 40 +++++++++++++++++++
12 files changed, 448 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-extended/ghostscript/arm/objarch.h
create mode 100644 meta/recipes-extended/ghostscript/arm/soobjarch.h
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/ghostscript-9.02-genarch.patch
create mode 100644 meta/recipes-extended/ghostscript/i586/objarch.h
create mode 100644 meta/recipes-extended/ghostscript/i586/soobjarch.h
create mode 100644 meta/recipes-extended/ghostscript/mips/objarch.h
create mode 100644 meta/recipes-extended/ghostscript/mips/soobjarch.h
create mode 100644 meta/recipes-extended/ghostscript/powerpc/objarch.h
create mode 100644 meta/recipes-extended/ghostscript/powerpc/soobjarch.h
create mode 100644 meta/recipes-extended/ghostscript/x86_64/objarch.h
create mode 100644 meta/recipes-extended/ghostscript/x86_64/soobjarch.h
--
1.7.5.1.300.gc565c
next reply other threads:[~2011-05-21 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 8:24 Kang Kai [this message]
2011-05-21 8:24 ` [PATCH 1/1] ghostscript: fix run failure on mpc8315e Kang Kai
2011-05-25 17:59 ` [PATCH 0/1]ghostscript: add patches to make it run cross compile platform V2 Saul Wold
2011-06-01 5:13 ` Saul Wold
2011-06-01 6:48 ` Kang Kai
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.1305963432.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.