All of lore.kernel.org
 help / color / mirror / Atom feed
From: "yue.tao" <yue.tao@windriver.com>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] waf.bbclass: correct the searching patch of waf
Date: Fri, 25 May 2018 18:33:59 +0800	[thread overview]
Message-ID: <5B07E697.5070900@windriver.com> (raw)
In-Reply-To: <CAJdd5GYqp=urzru6H8EuTtS63QxjGC7BMntuV10w+KXediE9-w@mail.gmail.com>

You're correct. After updating the last commit of meta-oe, the commit 
below has already fixed this issue. Thank Watt.


commit 29e280ee11c9a6f13c004ff25299668e4616f275
Author: Joshua Watt <jpewhacker@gmail.com>
Date:   Mon Feb 12 10:20:41 2018 -0600

     waf-samba.bbclass: No longer inherit waf.bbclass

     waf-samba.bbclass uses waf in a very different way than the "standard"
     method that waf.bbclass targets and ends getting very little useful
     functionality from that class.

     Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
     Signed-off-by: Armin Kuster <akuster808@gmail.com>


Thanks,
yue.tao


On 2018年05月25日 11:46, Joshua Watt wrote:
>
>
> On Thu, May 24, 2018, 22:10 Yue Tao <Yue.Tao@windriver.com
> <mailto:Yue.Tao@windriver.com>> wrote:
>
>     The waf is localed at ${S}/buildtools/bin/, not ${S}. Update the
>     subsrcdir to look for the right path. The WARNINGs below can be fixed
>     by the fix.
>
>     WARNING: lib32-libtalloc-2.1.9-r0 do_configure: Unable to execute
>     waf --version, exit code 127. Assuming waf version without
>     bindir/libdir support.
>     WARNING: lib32-libtdb-1.3.14-r0 do_configure: Unable to execute waf
>     --version, exit code 127. Assuming waf version without bindir/libdir
>     support.
>     WARNING: lib32-libtevent-0.9.31-r0 do_configure: Unable to execute
>     waf --version, exit code 127. Assuming waf version without
>     bindir/libdir support.
>     WARNING: lib32-libldb-1.1.29-r0 do_configure: Unable to execute waf
>     --version, exit code 127. Assuming waf version without bindir/libdir
>     support.
>     WARNING: lib32-samba-4.6.7-r0 do_configure: Unable to execute waf
>     --version, exit code 127. Assuming waf version without bindir/libdir
>     support.
>
>     Signed-off-by: Yue Tao <Yue.Tao@windriver.com
>     <mailto:Yue.Tao@windriver.com>>
>     ---
>       meta/classes/waf.bbclass | 2 +-
>       1 file changed, 1 insertion(+), 1 deletion(-)
>
>     diff --git a/meta/classes/waf.bbclass b/meta/classes/waf.bbclass
>     index 19e93761b3..f8e66835fb 100644
>     --- a/meta/classes/waf.bbclass
>     +++ b/meta/classes/waf.bbclass
>     @@ -7,7 +7,7 @@ python waf_preconfigure() {
>           import subprocess
>           from distutils.version import StrictVersion
>           subsrcdir = d.getVar('S')
>     -    wafbin = os.path.join(subsrcdir, 'waf')
>     +    wafbin = os.path.join(subsrcdir + '/buildtools/bin/', 'waf')
>
>
> NACK. ${S}/waf is the "standard" location for waf, if your recipe has it
> in a different location, you need to parameterize it. Probably something
> like:
>
>   WAF ?= "${S}/waf"
>
> However, I thought these recipes were inheriting from waf-samba.bbclass
> which already does the right thing. Perhaps you have an outdated version
> of meta-oe?
>
>           try:
>               result = subprocess.check_output([wafbin, '--version'],
>     cwd=subsrcdir, stderr=subprocess.STDOUT)
>               version = result.decode('utf-8').split()[1]
>     --
>     2.17.0
>
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



      reply	other threads:[~2018-05-25 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  3:09 [PATCH] waf.bbclass: correct the searching patch of waf Yue Tao
2018-05-25  3:46 ` Joshua Watt
2018-05-25 10:33   ` yue.tao [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=5B07E697.5070900@windriver.com \
    --to=yue.tao@windriver.com \
    --cc=jpewhacker@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 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.