Or use one of the CROPS docker containers with gcc6
On Thu, Oct 12, 2017 at 8:48 PM Khem Raj wrote:
> On Fri, Oct 13, 2017 at 01:21:10AM +, Denys Dmytriyenko wrote:
> > Khem,
> >
> > I tried following on your suggestion to add #include , but it is
> > already there in
On Thu, Oct 12, 2017 at 07:25:44AM +, Jonathan Liu wrote:
> ${bindir}/npx is a symbolic link to npm-cli.js in the npm module.
> This avoids the nodejs package depending on nodejs-npm.
>
> Signed-off-by: Jonathan Liu
> ---
> meta-oe/recipes-devtools/nodejs/nodejs_8.4.0.bb |
On Fri, Oct 13, 2017 at 01:21:10AM +, Denys Dmytriyenko wrote:
> Khem,
>
> I tried following on your suggestion to add #include , but it is
> already there in src/corelib/global/qnumeric_p.h
>
> Not sure why target qtbase builds fine with oe-core gcc 6.3.0, but
> nativesdk-qtbase fails
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!|Signatures
!!colspan='15'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
Khem,
I tried following on your suggestion to add #include , but it is
already there in src/corelib/global/qnumeric_p.h
Not sure why target qtbase builds fine with oe-core gcc 6.3.0, but
nativesdk-qtbase fails with this error... Any more ideas? Thanks.
--
Denys
On Tue, Oct 03, 2017 at
From: Denys Dmytriyenko
oe-core will focus on perf as a better alternative moving forward. Existing
users of oprofile are encouraged to move to perf, but for now can be unblocked
with oprofile moved to meta-oe.
Signed-off-by: Denys Dmytriyenko
---
On Tue, Oct 03, 2017 at 03:19:46PM -0400, Denys Dmytriyenko wrote:
> On Tue, Oct 03, 2017 at 09:52:51AM +0200, Martin Jansa wrote:
> > Yes, I've seen this few times as well.
>
> Ok, for now I had to manually build pseudo-native to seed sstate cache to
> overcome this issue. Otherwise building a
On Thu, Oct 12, 2017 at 07:56:25AM -0500, Aníbal Limón wrote:
> From: Aníbal Limón
>
> A tool to generate load and stress a system, currently this recipe
> is on a couple of layers [1] and is not updated, a good reason to
> have in meta-oe.
>
> [1]
>
From: Denys Dmytriyenko
ptest.bbclass provides a set of standard do_*_ptest_base tasks. Each of
them calls a corresponding regular do_*_ptest task, that components are
supposed to override for own implementation. When PTEST_ENABLED is not
set, an anonymous python function removes
On Thu, Oct 12, 2017 at 12:04 AM, Khem Raj wrote:
> On Wed, Oct 11, 2017 at 7:31 AM, Aníbal Limón
> wrote:
> > From: Aníbal Limón
> >
> > A tool to generate load and stress a system, currently this recipe
> > is on a couple
Hi Mikko
> I'll check if we could share our branch to bring Qt 5.6.2 base to jethro
which is mostly just cherry-picked patches from krogoth branch.
That's great and qt company is also managed qt 5.6.x in 5.6 branch of their
repository (http://code.qt.io/cgit/yocto/meta-qt5.git/)
Thanks
Version 5.8 does no longer includes the facebook patent grant and is
licensed under the Apache-2.0 or GPL-2.0 license.
Tests and tools don't compile on armv5 so we disable them.
The tools are never installed anyway so it doesn't make a difference for
the resulting package.
Signed-off-by: Pascal
${bindir}/npx is a symbolic link to npm-cli.js in the npm module.
This avoids the nodejs package depending on nodejs-npm.
Signed-off-by: Jonathan Liu
---
meta-oe/recipes-devtools/nodejs/nodejs_8.4.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Oct 12, 2017 at 10:03:01AM +0900, Changhyeok Bae wrote:
> Hi maintainers
>
> Qt 5.6 is LTS version and not GPL3 license.
> So why don't you keep v5.6.x in master branch?
> Many companies, opensource projects and developers would like to use Qt
> v5.6 in master branch to use it with latest
14 matches
Mail list logo