All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1]ghostscript: add patches to make it run cross compile platform V2
Date: Wed, 1 Jun 2011 14:48:40 +0800	[thread overview]
Message-ID: <4DE5E0C8.4070909@windriver.com> (raw)
In-Reply-To: <4DE5CA77.3050907@linux.intel.com>

On 2011年06月01日 13:13, Saul Wold wrote:
> On 05/21/2011 01:24 AM, Kang Kai wrote:
>> 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)
>>
>
Hi Saul,

>
> I think I must have merged the working patch, when I started to test 
> with your enable ghostscipt patch I got a fetch error on ghostscript, 
> I think we some how missed the changes you made for obarch.h and 
> soobjarch.h
>
> I get the following error:ERROR: Logfile of failure stored in:
>
> /intel/poky/builds/world/tmp/work/i686-linux/ghostscript-native-9.02-r1/temp/log.do_fetch.11982 
>
> Log data follows:
> | ERROR: Function 'Fetcher failure for URL: 'file://objarch.h'. Unable 
> to fetch URL file://objarch.h from any source.' failed
> | ERROR: Function 'Fetcher failure for URL: 'file://objarch.h'. Unable 
> to fetch URL file://objarch.h from any source.' failed
> NOTE: package ghostscript-native-9.02-r1: task do_fetch: Failed
> ERROR: Task 343 
> (virtual:native:/intel/poky/distro/meta/recipes-extended/ghostscript/ghostscript_9.02.bb, 
> do_fetch) failed with exit code '1'
The reason cause failure is your build machine arch is "i686" not 
provided by ghostscript source files. And run 'cp i586 i686' will fix 
this issue.

But I am not sure this is the right solution, it should not be affected 
by build machine. For example, if somebody build yocto on a i486 
machine, it will fail too.

Maybe I need to remove the native package dependency just like what is 
done in oe's gs recipe and send it later.

Thanks & Regards,
Kai
>
>
> Please review your ghostscript and verify that it is correct.
>
> Thanks
> Sau!
>
>> 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
>>



      reply	other threads:[~2011-06-01  6:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21  8:24 [PATCH 0/1]ghostscript: add patches to make it run cross compile platform V2 Kang Kai
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 [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=4DE5E0C8.4070909@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=sgw@linux.intel.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 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.