In the linux-yocto_3.0.bb recipe we have:
meta/recipes-kernel/linux/linux-yocto_3.0.bb:SRC_URI =
"git://git.pokylinux.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
Should this really be git.yoctoproject.org?
[ I think the sites might be interchangeable,
On Aug 9, 2011, at 11:18 PM, Darren Hart wrote:
> Bruce,
>
> The following patch is needed for qemuppc and fsl-mpc8315e-rdb (same
> reasons as before). Can you pull this in from the 2.6.37 yocto tree?
>
> commit 5ff609967ffe87c49d534d7861a7e0b150517726
> Author: Bruce Ashfield
> Date: Thu Oc
Is there some command to get the set of packages that will be attempted to be
built?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
>> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
>>
>> My question still stands even w/o it being in formal docs.
>
> FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes.
> I'd be interested to know where we've missed the references to it and
> ge
On Aug 3, 2011, at 10:12 AM, Richard Purdie wrote:
> On Wed, 2011-08-03 at 09:50 -0500, Kumar Gala wrote:
>> On Aug 3, 2011, at 9:22 AM, Richard Purdie wrote:
>>
>>> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote:
>>>> Bug submitted:
>>>>
&g
On Aug 3, 2011, at 9:22 AM, Richard Purdie wrote:
> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote:
>> Bug submitted:
>>
>> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
>>
>> My question still stands even w/o it being in formal docs.
>
> F
On Aug 3, 2011, at 9:29 AM, Paul Eggleton wrote:
> On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote:
>> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote:
>>> Bug submitted:
>>>
>>> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
>>>
&
ave to learn more about the context of the problem from
> someone. The bug could just be against documentation in general and specify
> the need for "better documentation using a prebuilt toolchain."
>
> ScottR
>
> -Original Message-
> From: Kumar Gala [mail
On Aug 2, 2011, at 10:53 PM, Kumar Gala wrote:
> One of my Chinese colleagues mentioned he was not able to get to the
> http://www.yoctoproject.org/ website. I was wondering if anyone else might
> be experience this or not?
>
> Is this something someone at LF can look into?
One of my Chinese colleagues mentioned he was not able to get to the
http://www.yoctoproject.org/ website. I was wondering if anyone else might be
experience this or not?
Is this something someone at LF can look into?
- k
___
yocto mailing list
yocto
I can, but not sure what the bug is.
- k
On Jul 28, 2011, at 11:39 PM, Stewart, David C wrote:
> Scott - I have had a couple of questions about this exact topic. Can you
> please submit a bug on this? Thanks.
>
> Sent from my Blackberry
>
> - Original Message -----
On Jul 28, 2011, at 2:04 PM, Phil Blundell wrote:
> On Thu, 2011-07-28 at 20:54 +0200, Martin Jansa wrote:
>> this change causes ERROR here with nokia900:
>> Error, the PACKAGE_ARCHS variable contains duplicates. The following archs
>> are listed more than once: armv7a-vfp-neon
>
> It isn't tot
On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
> On 07/28/2011 08:45 AM, Kumar Gala wrote:
>> I think I know the cause, let me dig up the change that is related. What
>> bit is looking for just ppc603e?
>>
> This might also be related to the PACKAGE_EXTRA_ARCHS issue,
I have, it doesn't help. I believe its partly due to how we are appending to
TUNE_PKGARCH, but what's not clear to me is what case is failing and looking
for just ppc603e instead of powerpcppc603e
- k
On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
> On 07/28/2011 08:45 AM, Kum
/powerpcppc603e to
> ${BUILD_DIR}/deploy/rpm/ppc603e.
>
> I will let you know as soon as I find the cause.
>
> Regards
>
> Malcolm
>
> -Original Message-
> From: yocto-boun...@yoctoproject.org
> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar
Anyone got any ideas about the following:
| ERROR: Function 'do_rootfs' failed (see
/local/home/galak/git/poky/build/tmp/work/mpc8315e_rdb-poky-linux/core-image-minimal-1.0-r0/temp/log.do_rootfs.19834
for fu
rther information)
| Generating solve db for
/local/home/galak/git/poky/build/tmp/deplo
It seems like there is a way to use a prebuilt toolchain with poky but no real
details.
Some refs in the docs like:
POKYMODE
Toolchain selector. It can be external toolchain built from Poky or few
supported combinations of upstream GCC or CodeSourcery Labs toolchain.
But grepping the code ther
Is it normal that the first stage (native) portion does not seem to either deal
with BB_NUMBER_THREADS or PARALLEL_MAKE?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
I was wondering what distinction qualified for a BSP existing in a meta layer
vs in poky directly.
For FSL PPC we currently have MPC8315-RDB in poky. Ideally we'd have one BSP
for each major flavor [ associated with a unique compiler / libc target ].
This would end up being something like P20
On Jul 27, 2011, at 9:06 AM, Tom Zanussi wrote:
> On Wed, 2011-07-27 at 06:53 -0700, Kumar Gala wrote:
>> On Jul 27, 2011, at 8:50 AM, Tom Zanussi wrote:
>>
>>> Hi Kumar,
>>>
>>> For meta-intel, it's pretty simple and is summarized by this
> Hi Kumar,
>
> As you know, I've been working on several kernel efforts
> around the FSL parts as well (in particular the ones that
> have enough pieces upstream to work out of the box). I
> definitely don't want to overlap in a way that doesn't
> create complimentary efforts.
>
> What are your
On Jul 27, 2011, at 8:50 AM, Tom Zanussi wrote:
> Hi Kumar,
>
> For meta-intel, it's pretty simple and is summarized by this blurb from
> the meta-intel MAINTAINERS file:
>
> "Please submit any patches against meta-intel BSPs to the Yocto mailing
> list (yocto@yoctoproject.org)."
>
> Basicall
On Jul 27, 2011, at 3:45 AM, Richard Purdie wrote:
> On Wed, 2011-07-27 at 00:21 -0500, Kumar Gala wrote:
>> Who is the best person to ask about adding new BSPs into yocto. What
>> I mean by this is having a meta layer hosted on git.yoctoproject.org
>> like meta-in
Who is the best person to ask about adding new BSPs into yocto. What I mean by
this is having a meta layer hosted on git.yoctoproject.org like meta-intel and
the mechanics associated with this (getting new repo on git server, autobuilder
support, webpage details, etc.).
- k
___
On Jul 14, 2011, at 11:56 PM, Kumar Gala wrote:
> The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
> floating point.
>
> 'SPE' floating point is what exists on the e500v2 core.
>
> Signed-off-by: Kumar Gala
> ---
> meta-yocto/conf/m
ignore not just build/* but any build*/* cases.
Signed-off-by: Kumar Gala
---
.gitignore | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/.gitignore b/.gitignore
index b13086d..d44e729 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,11 +1,11 @@
*.pyc
*.pyo
Richard,
I'm working on getting a ppc64 build going and looking close to having that
done. I was wondering what the state of multilib support was as I'd really
like to have that functional for the ppc64 system.
Think this will also be useful to flush out any multilib issues by having
another
For a new bsp/target what's the best config choice to try and build all of
yocto? Is it core-image-sato?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
> On 11-07-15 12:56 AM, Kumar Gala wrote:
>> The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
>> floating point.
>>
>> 'SPE' floating point is what exists on the e500v2 core.
>
On Jul 20, 2011, at 12:05 PM, Saul Wold wrote:
> On 07/19/2011 10:41 AM, Kumar Gala wrote:
>> The majority of support for the PowerPC e500v2/SPE target already
>> exists. However some minor cleans are required to get things working
>> completely.
>>
>> The
Its possible that BASE_PACKAGE_ARCH isn't set to ppce500 or ppce500v2 when
we build native toolchains. So we can utilize TARGET_FPU being set to
'ppc-efd' or 'ppc-efs' to determine if we should enable the gnuspe ABI.
Signed-off-by: Kumar Gala
---
meta/conf/distro/
-maltivec
Which would cause the compile to fail due to the mutual exclusion.
Pulled in a patch from the debian SPE port that addresses this issue:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-June/010212.html
Signed-off-by: Kumar Gala
---
.../flac/flac-1.2.1/0001-No-
If trying to build for an e500v2 target openssl will fail to build since
the configure script didn't know how to handle a 'gnuspe' target.
Signed-off-by: Kumar Gala
---
meta/recipes-connectivity/openssl/openssl.inc |3 +++
.../recipes-connectivity/openssl/openssl_0.9.8r.
Signed-off-by: Kumar Gala
---
meta/conf/machine/include/tune-ppce500v2.inc |4
1 files changed, 4 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500v2.inc
* Removed TARGET_OS_powerpc (not needed)
diff --git a/meta/conf/machine/include/tune
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
completely.
The e500v2 utilizes a unique floating point programming model / ABI from
other PowerPC targets and thus requires special handling.
- k
__
The e500v2 core utilizes a unique floating point programming model / ABI.
We utilize TARGET_FPU = "ppc-efd" to distinguish this choice (Embedded
scalar single-precision floating-point). When building the toolchain for
this ABI we need configure gcc with --enable-e500_double.
Signed-off
On Jul 19, 2011, at 10:32 AM, Saul Wold wrote:
> On 07/19/2011 06:17 AM, Kumar Gala wrote:
>>
>> On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
>>
>>>
>>> Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
>>>
>>>&g
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
> On 07/18/2011 07:54 AM, Kumar Gala wrote:
>>
>> On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
>>
>>> On Mon, Jul 18, 2011 at 5:58 AM, Kumar Gala
>>> wrote:
>>>> I've been working on tryin
Adding openembedded-core to see if any feedback on my query.
- k
On Jul 19, 2011, at 1:47 AM, Kumar Gala wrote:
>
> On Jul 19, 2011, at 1:04 AM, Khem Raj wrote:
>
>> On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala
>> wrote:
>>> The e500v2 core utilizes a unique fl
On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
>
> Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
>
>> The majority of support for the PowerPC e500v2/SPE target already
>> exists. However some minor cleans are required to get things working
>> co
On Jul 19, 2011, at 1:04 AM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala
> wrote:
>> The e500v2 core utilizes a unique floating point programming model / ABI.
>> We utilize TARGET_FPU = "spe" to distinguish this choice. When building
>>
On Jul 19, 2011, at 1:08 AM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala
> wrote:
>> Its possible that BASE_PACKAGE_ARCH isn't set to ppce500 or ppce500v2 when
>> we build native toolchains. So we can utilize TARGET_FPU being set to
>> "spe
On Jul 19, 2011, at 1:01 AM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala
> wrote:
>> Signed-off-by: Kumar Gala
>> ---
>> meta/conf/machine/include/tune-ppce500v2.inc |5 +
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
Signed-off-by: Kumar Gala
---
meta/conf/machine/include/tune-ppce500mc.inc |4
1 files changed, 4 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500mc.inc
diff --git a/meta/conf/machine/include/tune-ppce500mc.inc
b/meta/conf/machine/include/tune
-maltivec
Which would cause the compile to fail due to the mutual exclusion.
Pulled in a patch from the debian SPE port that addresses this issue:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-June/010212.html
Signed-off-by: Kumar Gala
---
.../flac/flac-1.2.1/0001-No-
If trying to build for an e500v2 target openssl will fail to build since
the configure script didn't know how to handle a 'gnuspe' target.
Signed-off-by: Kumar Gala
---
meta/recipes-connectivity/openssl/openssl.inc |3 +++
.../recipes-connectivity/openssl/openssl_0.9.8r.
Signed-off-by: Kumar Gala
---
meta/conf/machine/include/tune-ppce500v2.inc |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500v2.inc
diff --git a/meta/conf/machine/include/tune-ppce500v2.inc
b/meta/conf/machine/include/tune
Its possible that BASE_PACKAGE_ARCH isn't set to ppce500 or ppce500v2 when
we build native toolchains. So we can utilize TARGET_FPU being set to
"spe" to determine if we should enable the gnuspe ABI.
Signed-off-by: Kumar Gala
---
meta/conf/distro/include/tclibc-eglibc.inc |
The e500v2 core utilizes a unique floating point programming model / ABI.
We utilize TARGET_FPU = "spe" to distinguish this choice. When building
the toolchain for this ABI we need configure gcc with --enable-e500_double.
Signed-off-by: Kumar Gala
---
meta/recipes-devtools/gcc/g
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
completely.
The e500v2 utilizes a unique floating point programming model / ABI from
other PowerPC targets and thus requires special handling.
- k
__
On Jul 18, 2011, at 2:27 PM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 12:22 PM, Kumar Gala
> wrote:
>>
>> On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
>>
>>> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala
>>> wrote:
>>>>>>
On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala
> wrote:
>>>>>>> You can try -fno-use-linker-plugin as a workaround. Does
>>>>>>> liblto_plugin.so exist on target rfs ?
>>>>>>>
> You can try -fno-use-linker-plugin as a workaround. Does
> liblto_plugin.so exist on target rfs ?
> it might be then gcc driver bug if the library is not there then we
> forgot to package it.
File appears to be there:
root@p2020-ds:/# file
/usr/libexec/gcc/po
On Jul 18, 2011, at 1:01 PM, Kumar Gala wrote:
>
> On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
>
>> On 07/18/2011 07:54 AM, Kumar Gala wrote:
>>>
>>> On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
>>>
>>>> On Mon, Jul 18, 2011 at 5:58 A
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
> On 07/18/2011 07:54 AM, Kumar Gala wrote:
>>
>> On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
>>
>>> On Mon, Jul 18, 2011 at 5:58 AM, Kumar Gala
>>> wrote:
>>>> I've been working on tryin
I was trying a core-image-minimal build with 'tools-sdk' added to
EXTRA_IMAGE_FEATURES and was expecting a native gcc in the generated rootfs.
This was for mpc8315e-rdb config.
conf/local.conf has:
EXTRA_IMAGE_FEATURES = "tools-sdk debug-tweaks"
Is this wrong? is my expectation wrong based o
On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
> On Mon, Jul 18, 2011 at 5:58 AM, Kumar Gala wrote:
>> I've been working on trying to get an e500v2 (linux-gnuspe) compiler working
>> and seem to have build a native toolchain. However when I try and compile a
>> simp
I've been working on trying to get an e500v2 (linux-gnuspe) compiler working
and seem to have build a native toolchain. However when I try and compile a
simple hello world style app I get:
root@p2020-ds:~# gcc float.c
gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
compil
On Jul 15, 2011, at 5:04 PM, Khem Raj wrote:
> On Fri, Jul 15, 2011 at 2:57 PM, Kumar Gala wrote:
>>
>> On Jul 15, 2011, at 4:29 PM, Khem Raj wrote:
>>
>>> On Fri, Jul 15, 2011 at 2:10 PM, Kumar Gala
>>> wrote:
>>>> In my attempts to get a
On Jul 15, 2011, at 4:29 PM, Khem Raj wrote:
> On Fri, Jul 15, 2011 at 2:10 PM, Kumar Gala wrote:
>> In my attempts to get an e500v2/gnuspe toolchain working I was able to get
>> core-image-minimal working. However when I try the 'meta-toolchain' I run
>> into
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
> On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala wrote:
>> Where is the best place to ask questions and try and get support for adding
>> some toolchain variations in?
>>
>> I'm wanting to add support in for a few d
In my attempts to get an e500v2/gnuspe toolchain working I was able to get
core-image-minimal working. However when I try the 'meta-toolchain' I run into
the following below. I believe this is because of TARGET_OS being
'linux-gnuspe'.
Any ideas ?
- k
[kumar@right build-p2020]$ bitbake meta
On Jul 15, 2011, at 8:37 AM, Richard Purdie wrote:
> On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
>> On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
>>
>>> Where is the best place to ask questions and try and get support for adding
>>> some toolchain va
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
> Where is the best place to ask questions and try and get support for adding
> some toolchain variations in?
>
> I'm wanting to add support in for a few different flavors of PPC that are not
> currently supported:
>
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
> On 11-07-15 12:56 AM, Kumar Gala wrote:
>> The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
>> floating point.
>>
>> 'SPE' floating point is what exists on the e500v2 core.
>
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.
'SPE' floating point is what exists on the e500v2 core.
Signed-off-by: Kumar Gala
---
meta-yocto/conf/machine/mpc8315e-rdb.conf |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
dif
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors of PPC that are not
currently supported:
* e500v2 (gcc needs --enable-e500_double, eglibc
* e5500 (64-bit embedded ppc)
* e5500 -
On Jul 14, 2011, at 11:24 AM, Bruce Ashfield wrote:
> On 07/14/11 12:21, Koen Kooi wrote:
>>
>> Op 14 jul 2011, om 18:20 heeft Kumar Gala het volgende geschreven:
>>
>>>
>>> On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:
>>>
>>>>
On Jul 14, 2011, at 8:52 AM, Richard Purdie wrote:
> On Thu, 2011-07-14 at 08:06 -0500, Kumar Gala wrote:
>> On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:
>>
>>> On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:
>>>> Hello list,
>>
On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:
> On 07/14/11 09:40, Koen Kooi wrote:
>>
>> Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:
>>
>>> On 07/14/11 09:05, Kumar Gala wrote:
>>>> Is there a list of which
On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:
> On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:
>> Hello list,
>>
>> Is there a interactive menu-based configuration for yocto/poky builds
>> similar to that provided in Buildroot? Or is someone working on this?
>
> At present there is
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in
the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is
supported or not.
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/
On Nov 10, 2010, at 8:23 AM, Bruce Ashfield wrote:
> On 10-11-10 09:11 AM, Kumar Gala wrote:
>>
>> On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
>>
>>> On 10-11-10 08:38 AM, Bruce Ashfield wrote:
>>>> On 10-11-10 01:46 AM, Kumar Gala wrote:
>
On Nov 10, 2010, at 7:50 AM, Richard Purdie wrote:
> On Wed, 2010-11-10 at 07:31 -0600, Kumar Gala wrote:
>> On Nov 10, 2010, at 7:29 AM, Richard Purdie wrote:
>>
>>> On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
>>>> ERROR: Task failed: Fetch f
On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
> On 10-11-10 08:38 AM, Bruce Ashfield wrote:
>> On 10-11-10 01:46 AM, Kumar Gala wrote:
>>> Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
>>> SPE. This isn't correct for an MPC8313 SoC.
&g
On Nov 10, 2010, at 7:29 AM, Richard Purdie wrote:
> On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
>> ERROR: Task failed: Fetch failed: Unable to fetch URL
>> cvs://anonym...@cvs.sv.gnu.org/cvsroot/config;module=config;method=pserver;date=20080123
>> from any sou
On Nov 10, 2010, at 6:20 AM, Tian, Kevin wrote:
>> From: Kumar Gala
>> Sent: Wednesday, November 10, 2010 2:42 PM
>>
>> I'm trying to build the MPC8135E RDB and have the following setup in
>> conf/local.conf:
>>
>> # Uncomment and set to
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as SPE. This
isn't correct for an MPC8313 SoC.
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
I'm trying to build the MPC8135E RDB and have the following setup in
conf/local.conf:
# Uncomment and set to allow bitbake to execute multiple tasks at once.
# For a quadcore, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate.
BB_NUMBER_THREADS = "16"
# Also, make can be pass
79 matches
Mail list logo
