public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: zhenbo <zhenbo.gao@windriver.com>
To: Bill Randle <bill.randle@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] perl: correct the path of perl used by ptest
Date: Fri, 9 Sep 2016 17:34:32 +0800	[thread overview]
Message-ID: <57D28228.6090206@windriver.com> (raw)
In-Reply-To: <CA+n--H_aSwgXXtNj8VJO3JxDs0zC5RiOXRAqLp=nL8Bpp16U0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]

Hi Bill,

Sorry that i just notice this email, sorry for the late reply.

I made this patch based on the following two points:
1. Please see commit 467eb93f and 84a39786, there has the following code 
in files automake_1.15.bb and autoconf.inc:
     CACHED_CONFIGUREVARS += "ac_cv_path_PERL=${USRBINPATH}/perl"
2. The familiar modifications for other files are accepted by oe-core, 
like gobject-introspection groff texi2html quilt and so on...

Thanks,
Zhenbo


On 2016年08月31日 22:42, Bill Randle wrote:
> Under what conditions is the explicit path to /usr/bin/perl required? 
> Just before your added code, it creates a symlink from the installed 
> perl location to the "t" directory where the tests are run. What if 
> the perl that was built was an alternate version and installed in 
> /usr/local/bin?
>
>     -Bill
>
> On Tue, Aug 30, 2016 at 10:37 PM, Zhenbo Gao <zhenbo.gao@windriver.com 
> <mailto:zhenbo.gao@windriver.com>> wrote:
>
>     some files from perl-ptest depends on perl, which is located at
>     /usr/bin/
>
>     Signed-off-by: Zhenbo Gao <zhenbo.gao@windriver.com
>     <mailto:zhenbo.gao@windriver.com>>
>     ---
>      meta/recipes-devtools/perl/perl-ptest.inc | 6 ++++++
>      1 file changed, 6 insertions(+)
>
>     diff --git a/meta/recipes-devtools/perl/perl-ptest.inc
>     b/meta/recipes-devtools/perl/perl-ptest.inc
>     index d136c5c..94e40e6 100644
>     --- a/meta/recipes-devtools/perl/perl-ptest.inc
>     +++ b/meta/recipes-devtools/perl/perl-ptest.inc
>     @@ -24,6 +24,12 @@ do_install_ptest () {
>
>             ln -sf ${bindir}/perl ${D}${PTEST_PATH}/t/perl
>
>     +       # perl is located at /usr/bin/
>     +       p='^#![/.]*perl'
>     +       files=`grep -E ${p} ${D} -nr | grep -v -E 'Binary|win32' |
>     cut -d ':' -f 1`
>     +       for f in ${files}; do
>     +               sed -i -e "s:${p}:#! ${USRBINPATH}/perl:g" ${f}
>     +       done
>      }
>
>      python populate_packages_prepend() {
>     --
>     1.9.1
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>     <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>


[-- Attachment #2: Type: text/html, Size: 4182 bytes --]

      reply	other threads:[~2016-09-09  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  5:37 [PATCH] perl: correct the path of perl used by ptest Zhenbo Gao
2016-08-31 14:42 ` Bill Randle
2016-09-09  9:34   ` zhenbo [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=57D28228.6090206@windriver.com \
    --to=zhenbo.gao@windriver.com \
    --cc=bill.randle@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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