Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: saul.wold@intel.com, kang.kai@windriver.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] ghostscript: upgrade to 9.14
Date: Tue, 17 Jun 2014 08:45:44 +0100	[thread overview]
Message-ID: <1402991144.562.83.camel@ted> (raw)
In-Reply-To: <5eefad6f95c56a863ec21422837f03899ea8931d.1402901435.git.hongxu.jia@windriver.com>

On Mon, 2014-06-16 at 16:16 +0800, Hongxu Jia wrote:
> - The LICENSE added AGPL for the font files (in Resource/Font);
> 
> - Rebase ghostscript-9.02-parallel-make.patch to 9.14
> 
> - Rebase ghostscript-native-fix-disable-system-libtiff.patch
>   since base/configure.ac has been moved to configure.ac.
>   http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=f1488c5aff54f37ee67759827d4298592af5dbc8
> 
> - Obsolete ghostscript-9.05-NOT-check-endian.patch, and add option
>   '--enable-little-endian'/'--enable-big-endian' conditionally to
>   intead.
>   http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=e76dc46756e89a14a3348bce12a633d32e4fa831
> 
> - Add base-genht.c-add-a-preprocessor-define-to-allow-fope.patch
>   for native, since the upstream replace all fopen calls with
>   gp_fopen and add a preprocessor define so that any unintential
>   calls directly to fopen will cause an error. This patch add a
>   preprocessor define to allow fopen calling in base/genht.c as
>   exceptions.
>   http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=773c69e46e70bdd5482676437dafd2ca83397643
> 
> - Remove package ghostscript-cups, since CUPS filters
>   gstoraster and gstopxl has been moved to cups-filters
>   which is a free software package hosted by OpenPrinting.
>   http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=9304a21699a6c17579fae32f44f5c92a37c13e2d
>   http://www.linuxfoundation.org/collaborate/workgroups/openprinting/cups-filters
> 
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>  ...c-add-a-preprocessor-define-to-allow-fope.patch |  36 ++++++
>  .../ghostscript-9.02-parallel-make.patch           | 144 ++++++++++-----------
>  .../ghostscript-9.05-NOT-check-endian.patch        |  44 -------
>  ...tscript-native-fix-disable-system-libtiff.patch |  45 +++----
>  .../{ghostscript_9.07.bb => ghostscript_9.14.bb}   |  42 ++----
>  5 files changed, 132 insertions(+), 179 deletions(-)
>  create mode 100644 meta/recipes-extended/ghostscript/ghostscript/base-genht.c-add-a-preprocessor-define-to-allow-fope.patch
>  delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/ghostscript-9.05-NOT-check-endian.patch
>  rename meta/recipes-extended/ghostscript/{ghostscript_9.07.bb => ghostscript_9.14.bb} (70%)

This triggered a build failure:

https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/134/steps/BuildImages/logs/stdio

Cheers,

Richard



  reply	other threads:[~2014-06-17  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16  8:16 [PATCH 0/1] ghostscript: upgrade to 9.14 Hongxu Jia
2014-06-16  8:16 ` [PATCH 1/1] " Hongxu Jia
2014-06-17  7:45   ` Richard Purdie [this message]
2014-06-17  8:31     ` Hongxu Jia

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=1402991144.562.83.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hongxu.jia@windriver.com \
    --cc=kang.kai@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox