From: Hongxu Jia <hongxu.jia@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 6/6] groff: upgrade 1.22.3
Date: Thu, 25 Dec 2014 17:05:46 +0800 [thread overview]
Message-ID: <549BD36A.5080505@windriver.com> (raw)
In-Reply-To: <1419497071.6428.20.camel@linuxfoundation.org>
On 12/25/2014 04:44 PM, Richard Purdie wrote:
> On Thu, 2014-12-25 at 10:19 +0800, Hongxu Jia wrote:
>> Rebase groff-1.22.2-correct-man.local-install-path.patch to 1.22.3
>>
>> Refer what debian did, we add perl to RRECOMMENDS_${PN}, here is the
>> explanation in groff 1.22.3 README:
>> ...
>> Additionally, producing `PDF' output directly with the `gropdf' device needs
>> a working installation of `perl'. The same is true for some other
>> preprocessors like `chem'.
>> ...
>>
>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
>> ---
>> ...off-1.22.2-correct-man.local-install-path.patch | 32 ---------------
>> .../groff-correct-man.local-install-path.patch | 45 ++++++++++++++++++++++
>> .../groff/{groff_1.22.2.bb => groff_1.22.3.bb} | 7 ++--
>> 3 files changed, 49 insertions(+), 35 deletions(-)
>> delete mode 100644 meta/recipes-extended/groff/groff-1.22.2/groff-1.22.2-correct-man.local-install-path.patch
>> create mode 100644 meta/recipes-extended/groff/groff-1.22.3/groff-correct-man.local-install-path.patch
>> rename meta/recipes-extended/groff/{groff_1.22.2.bb => groff_1.22.3.bb} (89%)
> Given the original error message, if you build this on a machine
> with /bin/perl, does it not still give an error at rootfs time?
>
> Do we need to correctly set the path to perl in the recipe?
Got it, I will fix it. V3 incoming
//Hongxu
> Cheers,
>
> Richard
>
>
prev parent reply other threads:[~2014-12-25 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 5:09 [PATCH 0/6] Packages upgrade Hongxu Jia
2014-12-23 5:09 ` [PATCH 1/6] libxml2: upgrade to 2.9.2 Hongxu Jia
2014-12-23 5:09 ` [PATCH 2/6] directfb: upgrade to 1.7.6 Hongxu Jia
2014-12-25 22:02 ` Richard Purdie
2014-12-25 22:58 ` Otavio Salvador
2014-12-26 1:42 ` Hongxu Jia
2014-12-23 5:09 ` [PATCH 3/6] apr-util: upgrade to 1.5.4 Hongxu Jia
2014-12-23 5:09 ` [PATCH 4/6] pax-utils: upgrade to 0.9.2 Hongxu Jia
2014-12-23 5:09 ` [PATCH 5/6] ppp: upgrade 2.4.7 Hongxu Jia
2014-12-23 5:09 ` [PATCH 6/6] groff: upgrade 1.22.3 Hongxu Jia
2014-12-24 17:56 ` Saul Wold
2014-12-25 1:35 ` Hongxu Jia
2014-12-25 2:19 ` [PATCH V2 " Hongxu Jia
2014-12-25 2:23 ` Hongxu Jia
2014-12-25 8:44 ` Richard Purdie
2014-12-25 9:05 ` Hongxu Jia [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=549BD36A.5080505@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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