From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 0/4] Packages upgrade: groff and directfb
Date: Mon, 12 Jan 2015 10:04:43 +0800 [thread overview]
Message-ID: <54B32BBB.7050301@windriver.com> (raw)
In-Reply-To: <CAJTo0LacBzaWR933BAViPfMqR5cc+6O-PJBwmjCV4PSjJhJXXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On 01/09/2015 08:42 PM, Burton, Ross wrote:
>
> On 29 December 2014 at 05:47, Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>> wrote:
>
> Hongxu Jia (4):
> groff: upgrade 1.22.3
> groff: fix native perl path
> directfb: upgrade to 1.7.6
> qt4-embedded: support c++0x stand for directfb
>
>
> I've merged all of these into MUT apart from "groff: fix native perl
> path". Adding a dependency on perl-native seems like a massive
> overkill when the problem appears to me that we just need to ensure
> that all Perl scripts in ${bindir} get fixed, or that we set PERL
> appropriately. Setting PERL seems to be the right solution but we
> need it set for target builds only, so would this work?
>
> EXTRA_OECONF_append_class-target="PERL=${bindir}/perl"
Agree
//Hongxu
>
> Ross
[-- Attachment #2: Type: text/html, Size: 2355 bytes --]
prev parent reply other threads:[~2015-01-12 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 5:47 [PATCH V2 0/4] Packages upgrade: groff and directfb Hongxu Jia
2014-12-29 5:47 ` [PATCH 1/4] groff: upgrade 1.22.3 Hongxu Jia
2014-12-29 5:47 ` [PATCH 2/4] groff: fix native perl path Hongxu Jia
2014-12-29 5:47 ` [PATCH 3/4] directfb: upgrade to 1.7.6 Hongxu Jia
2014-12-29 5:47 ` [PATCH 4/4] qt4-embedded: support c++0x stand for directfb Hongxu Jia
2015-01-09 11:50 ` [PATCH V2 0/4] Packages upgrade: groff and directfb Hongxu Jia
2015-01-09 12:42 ` Burton, Ross
2015-01-12 2:04 ` 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=54B32BBB.7050301@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.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.