Re: [oe] libtalloc failure due to waf

I automatically sync about 12 layers every day. This is a show stopper because it breaks that workflow and forces a deviation from just building on “master”. I am now about two months behind “master” for various reasons, but this is the one remaining blocker. I have zero interest in carrying local

Re: [oe] libtalloc failure due to waf

+Joe who will merge it to meta-networking maybe you meant show stopper as libtalloc failure not the whole OE world failing to parse because of waf-samba.bbclass (even if you don't build any recipes using it). FWIW: I've also sent simple fix for that to oe-core a while ago:

Re: [oe] libtalloc failure due to waf

I've merged the fix for parsing issues immediately after sending it (6 days ago): http://git.openembedded.org/meta-openembedded/commit/?id=2f7de931885c1b9e63c4e4238f0f7ad1388e8b6d So it shouldn't fail to parse for you if you use new enough oe-core (it doesn't fail for me). waf.bbclass is still

Re: [oe] libtalloc failure due to waf

On Wed, Feb 21, 2018 at 8:48 PM, Tim Orling wrote: > Still failing for me, which is a show stopper. :( Armin has it in his testing branch for the next master update, so hopefully it will pulled in soon. > >> On Feb 21, 2018, at 5:36 PM, Denys Dmytriyenko

Re: [oe] libtalloc failure due to waf

Still failing for me, which is a show stopper. :( > On Feb 21, 2018, at 5:36 PM, Denys Dmytriyenko wrote: > > Any updates on this one yet? Thanks. > > On Fri, Feb 16, 2018 at 02:18:32PM -0800, Tim Orling wrote: >> Expediting the fix is greatly appreciated. >> >> Thank you! >>

Re: [oe] libtalloc failure due to waf

Any updates on this one yet? Thanks. On Fri, Feb 16, 2018 at 02:18:32PM -0800, Tim Orling wrote: > Expediting the fix is greatly appreciated. > > Thank you! > > --Tim > > On Fri, Feb 16, 2018 at 1:00 PM, Joshua Watt wrote: > > > On Fri, 2018-02-16 at 21:55 +0100, Martin

Re: [oe] libtalloc failure due to waf

Expediting the fix is greatly appreciated. Thank you! --Tim On Fri, Feb 16, 2018 at 1:00 PM, Joshua Watt wrote: > On Fri, 2018-02-16 at 21:55 +0100, Martin Jansa wrote: > > Don't you want to update that one to use the new function from utils > > instead of re-introducing

Re: [oe] libtalloc failure due to waf

On Fri, 2018-02-16 at 21:55 +0100, Martin Jansa wrote: > Don't you want to update that one to use the new function from utils > instead of re-introducing get_waf_parallel_make? yes. I guess I can do that now. It didn't exist when I wrote the first version of this patch > On Fri, Feb 16, 2018

Re: [oe] libtalloc failure due to waf

Don't you want to update that one to use the new function from utils instead of re-introducing get_waf_parallel_make? On Fri, Feb 16, 2018 at 9:18 PM, Joshua Watt wrote: > On Fri, 2018-02-16 at 21:08 +0100, Martin Jansa wrote: > > And now it will fail to parse as well: > >

Re: [oe] libtalloc failure due to waf

On Fri, 2018-02-16 at 21:08 +0100, Martin Jansa wrote: > And now it will fail to parse as well: > http://git.openembedded.org/openembedded-core/commit/?id=ccd1142d22b3 > 1ed85d8823b1bc9e11ccfd72b61f > > removed get_waf_parallel_make from waf.bbclass, so now all waf- > samba.bbclass users will

Re: [oe] libtalloc failure due to waf

And now it will fail to parse as well: http://git.openembedded.org/openembedded-core/commit/?id=ccd1142d22b31ed85d8823b1bc9e11ccfd72b61f removed get_waf_parallel_make from waf.bbclass, so now all waf-samba.bbclass users will fail to parse with: bb.data_smart.ExpansionError: Failure expanding

Re: [oe] libtalloc failure due to waf

Check this thread: http://lists.openembedded.org/pipermail/openembedded-commits/2018-January/218460.html but my patch wasn't merged: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146974.html only the one from Joshua. The original issue is still in rocko as well, the

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 06:37:11PM -0600, Joshua Watt wrote: > On Feb 15, 2018 17:42, "Denys Dmytriyenko" wrote: > > On Thu, Feb 15, 2018 at 03:30:06PM -0800, Khem Raj wrote: > > On Thu, Feb 15, 2018 at 3:24 PM, Denys Dmytriyenko > wrote: > > > On Thu, Feb 15,

Re: [oe] libtalloc failure due to waf

On Feb 15, 2018 17:42, "Denys Dmytriyenko" wrote: On Thu, Feb 15, 2018 at 03:30:06PM -0800, Khem Raj wrote: > On Thu, Feb 15, 2018 at 3:24 PM, Denys Dmytriyenko wrote: > > On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: > >> Then why did ‘sudo dnf

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 03:24:16PM -0800, Andre McCurdy wrote: > On Thu, Feb 15, 2018 at 3:10 PM, Tim Orling wrote: > > Seeing the same and trying to figure it out. Also, seems there is no recipe > > for waf-native, so it becomes a new required host tool. > > On Thu, Feb 15,

Re: [oe] libtalloc failure due to waf

On Thu, 2018-02-15 at 18:24 -0500, Denys Dmytriyenko wrote: > On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: > > Then why did ‘sudo dnf install waf’ get me past the error above? > > And why > > does Fedora have a package for it? > > > > https://src.fedoraproject.org/rpms/waf > > > >

Re: [oe] libtalloc failure due to waf

On Thu, 2018-02-15 at 23:20 +, Tim Orling wrote: > Then why did ‘sudo dnf install waf’ get me past the error above? And > why does Fedora have a package for it? > > https://src.fedoraproject.org/rpms/waf There is a... complicated history (which I am not a part of) between the maintainers

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 03:30:06PM -0800, Khem Raj wrote: > On Thu, Feb 15, 2018 at 3:24 PM, Denys Dmytriyenko wrote: > > On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: > >> Then why did ‘sudo dnf install waf’ get me past the error above? And why > >> does Fedora

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 06:24:40PM -0500, Denys Dmytriyenko wrote: > On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: > > Then why did ‘sudo dnf install waf’ get me past the error above? And why > > does Fedora have a package for it? > > > > https://src.fedoraproject.org/rpms/waf > >

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 3:24 PM, Denys Dmytriyenko wrote: > On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: >> Then why did ‘sudo dnf install waf’ get me past the error above? And why >> does Fedora have a package for it? >> >> https://src.fedoraproject.org/rpms/waf

Re: [oe] libtalloc failure due to waf

looks through the waf-apache thread. Once that lands in master you should be ok On Thu, Feb 15, 2018 at 2:53 PM, Denys Dmytriyenko wrote: > Hi, > > I'm getting below stack dump building libtalloc 2.1.10 in master. Works fine > in > rocko with libtalloc 2.1.9. I need it for

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 11:20:49PM +, Tim Orling wrote: > Then why did ‘sudo dnf install waf’ get me past the error above? And why > does Fedora have a package for it? > > https://src.fedoraproject.org/rpms/waf > > Regardless, something broke. I thought so too. As waf.bbclass from oe-core

Re: [oe] libtalloc failure due to waf

On Thu, 2018-02-15 at 23:10 +, Tim Orling wrote: > Seeing the same and trying to figure it out. Also, seems there is no > recipe > for waf-native, so it becomes a new required host tool. There is no "waf" tool, so a "waf-native" tool doesn't make sense... it's not how waf works. Each project

Re: [oe] libtalloc failure due to waf

Then why did ‘sudo dnf install waf’ get me past the error above? And why does Fedora have a package for it? https://src.fedoraproject.org/rpms/waf Regardless, something broke. On Thu, Feb 15, 2018 at 3:16 PM Joshua Watt wrote: > On Thu, 2018-02-15 at 23:10 +, Tim

Re: [oe] libtalloc failure due to waf

On Thu, Feb 15, 2018 at 3:10 PM, Tim Orling wrote: > Seeing the same and trying to figure it out. Also, seems there is no recipe > for waf-native, so it becomes a new required host tool. > On Thu, Feb 15, 2018 at 2:57 PM Denys Dmytriyenko wrote: > >> Hi, >>

Re: [oe] libtalloc failure due to waf

waf is generally shipped in the source tree, not used from any host. But I expect "[oe] [meta-networking][PATCH] waf-samba.bbclass: No longer inherit waf.bbclass” may be of interest here. On Thu, Feb 15, 2018 at 4:10 PM, Tim Orling wrote: > Seeing the same and trying to

Re: [oe] libtalloc failure due to waf

This was fixed here: http://lists.openembedded.org/pipermail/openembedd ed-devel/2018-February/116701.html I think it will probably be pushed to master soon, it is on the stagging/master-next branch in contrib (370ea5786) Joshua Watt On Thu, 2018-02-15 at 17:53 -0500, Denys Dmytriyenko wrote: >

Re: [oe] libtalloc failure due to waf

Seeing the same and trying to figure it out. Also, seems there is no recipe for waf-native, so it becomes a new required host tool. On Thu, Feb 15, 2018 at 2:57 PM Denys Dmytriyenko wrote: > Hi, > > I'm getting below stack dump building libtalloc 2.1.10 in master. Works > fine

[oe] libtalloc failure due to waf

Hi, I'm getting below stack dump building libtalloc 2.1.10 in master. Works fine in rocko with libtalloc 2.1.9. I need it for cifs-utils. I'm not familiar with waf, any help? Thanks. ERROR: libtalloc-2.1.10-r0 do_configure: Error executing a python function in exec_python_func()