From: "Huang, Jie (Jackie)" <Jackie.Huang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] enscript: set the correct path for perl
Date: Tue, 29 Aug 2017 01:13:13 +0000 [thread overview]
Message-ID: <1B858668EC6A94408DCA5225FDFA85AA014B889752@ALA-MBC.corp.ad.wrs.com> (raw)
In-Reply-To: <CA+chaQfG3sQW6mncedu36aeuWuckbmADjgVeCraU1dsXRAxWqg@mail.gmail.com>
Ok, please ignore mine if one of them is accepted.
Thanks,
Jackie
From: Martin Jansa [mailto:martin.jansa@gmail.com]
Sent: Tuesday, August 29, 2017 07:17
To: Khem Raj
Cc: Huang, Jie (Jackie); openembeded-devel
Subject: Re: [oe] [meta-oe][PATCH] enscript: set the correct path for perl
And also by:
https://patchwork.openembedded.org/patch/143340/
On Mon, Aug 28, 2017 at 5:26 PM, Khem Raj <raj.khem@gmail.com<mailto:raj.khem@gmail.com>> wrote:
On Sun, Aug 27, 2017 at 11:05 PM, <jackie.huang@windriver.com<mailto:jackie.huang@windriver.com>> wrote:
> From: Jackie Huang <jackie.huang@windriver.com<mailto:jackie.huang@windriver.com>>
>
> Set the correct path for perl and avoid
> searching the one in hosttools that cause
> QA issue:
>
> | ERROR: enscript-1.6.6-r0 do_package_qa: QA Issue: /usr/bin/diffpp
> contained in package enscript requires
> /builddir/tmp/hosttools/perl, but no providers found in RDEPENDS_enscript? [file-rdeps]
>
already fixed with https://patchwork.openembedded.org/patch/143281/
> Signed-off-by: Jackie Huang <jackie.huang@windriver.com<mailto:jackie.huang@windriver.com>>
> ---
> meta-oe/recipes-extended/enscript/enscript_1.6.6.bb<http://enscript_1.6.6.bb> | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-oe/recipes-extended/enscript/enscript_1.6.6.bb<http://enscript_1.6.6.bb> b/meta-oe/recipes-extended/enscript/enscript_1.6.6.bb<http://enscript_1.6.6.bb>
> index 96129880a..65f1ccfa0 100644
> --- a/meta-oe/recipes-extended/enscript/enscript_1.6.6.bb<http://enscript_1.6.6.bb>
> +++ b/meta-oe/recipes-extended/enscript/enscript_1.6.6.bb<http://enscript_1.6.6.bb>
> @@ -19,4 +19,6 @@ inherit autotools gettext
> SRC_URI[md5sum] = "3acc242b829adacabcaf28533f049afd"
> SRC_URI[sha256sum] = "6d56bada6934d055b34b6c90399aa85975e66457ac5bf513427ae7fc77f5c0bb"
>
> +CACHED_CONFIGUREVARS += "ac_cv_path_PERL=${bindir}/perl"
> +
> RDEPENDS_${PN} = "perl"
> --
> 2.11.0
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org<mailto:Openembedded-devel@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org<mailto:Openembedded-devel@lists.openembedded.org>
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2017-08-29 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 6:05 [meta-oe][PATCH] enscript: set the correct path for perl jackie.huang
2017-08-28 15:26 ` Khem Raj
2017-08-28 23:17 ` Martin Jansa
2017-08-29 1:13 ` Huang, Jie (Jackie) [this message]
2017-08-29 1:07 ` Huang, Jie (Jackie)
2017-08-29 1:11 ` Khem Raj
2017-08-29 1:13 ` Huang, Jie (Jackie)
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=1B858668EC6A94408DCA5225FDFA85AA014B889752@ALA-MBC.corp.ad.wrs.com \
--to=jackie.huang@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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.