From: Hongxu Jia <hongxu.jia@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>,
<ross.burton@intel.com>
Subject: Re: [PATCH 6/9] ghostscript: 9.16 -> 9.18
Date: Wed, 13 Jan 2016 09:44:20 +0800 [thread overview]
Message-ID: <5695ABF4.8080500@windriver.com> (raw)
In-Reply-To: <1452598749.28375.13.camel@linuxfoundation.org>
On 01/12/2016 07:39 PM, Richard Purdie wrote:
> On Mon, 2016-01-11 at 08:30 +0800, Hongxu Jia wrote:
>> Remove '--without-jbig2dec', since upstream did not
>> support it very well which caused build failure:
>> ...
>>> make[1]: *** No rule to make target `obj/sjbig2_.dev',
>> needed by `obj/sjbig2.dev'. Stop.
>> ...
>>
>> The same to option '--without-jbig2dec'.
>>
>> Already file a bug to upstream:
>> http://bugs.ghostscript.com/show_bug.cgi?id=696497
>>
>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> Presumably we use this option for a reason. What effect does removing
> it have? Should we backport the fixes instead?
The initial recipe has used this option without reason, The upstream
have replied the bug:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=4b7b278d
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b0f5a975
I will do the test and backport them in V2
//Hongxu
> Cheers,
>
> Richard
next prev parent reply other threads:[~2016-01-13 1:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 0:30 [PATCH 0/9] packages upgrade Hongxu Jia
2016-01-11 0:30 ` [PATCH 1/9] dhcp: 4.3.2 -> 4.3.3 Hongxu Jia
2016-01-11 0:30 ` [PATCH 2/9] elfutils: 0.163 -> 0.164 Hongxu Jia
2016-01-20 15:07 ` Maxin B. John
2016-01-20 17:16 ` Khem Raj
2016-01-21 3:23 ` Hongxu Jia
2016-01-11 0:30 ` [PATCH 3/9] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-12 1:14 ` Randy MacLeod
2016-01-12 1:22 ` Khem Raj
2016-01-12 2:38 ` Hongxu Jia
2016-01-11 0:30 ` [PATCH 4/9] xmlto: 0.0.26 -> 0.0.28 Hongxu Jia
2016-01-11 0:30 ` [PATCH 5/9] libgcrypt: 1.6.3 -> 1.6.4 Hongxu Jia
2016-01-11 0:30 ` [PATCH 6/9] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-12 11:39 ` Richard Purdie
2016-01-13 1:44 ` Hongxu Jia [this message]
2016-01-11 0:30 ` [PATCH 7/9] man-pages: 4.02 -> 4.04 Hongxu Jia
2016-01-11 0:30 ` [PATCH 8/9] help2man-native: 1.47.1 -> 1.47.3 Hongxu Jia
2016-01-11 0:30 ` [PATCH 9/9] gnupg: 2.1.7 -> 2.1.10 Hongxu Jia
2016-01-13 8:30 ` [PATCH V2] upgrade v2 pax-utils and v2 ghostscript Hongxu Jia
2016-01-13 8:30 ` [PATCH V2 3/9] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-13 8:30 ` [PATCH V2 6/9] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-17 17:44 ` Richard Purdie
2016-01-18 1:48 ` Hongxu Jia
2016-01-18 8:09 ` [PATCH V3 0/2] upgrade pax-utils and ghostscript Hongxu Jia
2016-01-18 8:09 ` [PATCH V2 1/2] pax-utils: 1.0.5 -> 1.1.4 Hongxu Jia
2016-01-18 8:09 ` [PATCH V3 2/2] ghostscript: 9.16 -> 9.18 Hongxu Jia
2016-01-13 8:48 ` [PATCH V2] upgrade v2 pax-utils and v2 ghostscript 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=5695ABF4.8080500@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@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.