Changelog since 2016-01-31 until 2016-02-07. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta-oe/recipes-support/ckermit/ckermit_302.bb
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
this explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta-oe/recipes-support/mg/mg_20110905.bb | 2
This recipe currently relies on EXTRA_OEMAKE having been to set to "-e
MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be changed.
Signed-off-by: Mike Crowe
---
meta-oe/recipes-devtools/iptraf/iptraf_3.0.0.bb
This series fixes various recipes that rely on the current default
value of EXTRA_OEMAKE = "-e MAKEFLAGS=" to explicitly set that value
in the hope that bitbake.conf can set EXTRA_OEMAKE = "" in the future.
The affected recipes are:
meta-multimedia/recipes-mkv/libebml/libebml_1.3.0.bb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While switching from fido to jethro we hit the next problem. :(
For one of our machines (based on Marvell Kirkwood, very similar to OpenRD) the
kernel build with the preferred gcc-5.2.0 does not boot. Immediately after the
kernel is started from
This patch fixes three problems
1) Running on a case-sensitive system would result in an error
due to invalid casing of pattern to install.
2) Using install on symlinks would cause multiple copies of the
same file to be installed on the target-system, since install
Signed-off-by: Philip Balister
---
.../libsodium/{libsodium_1.0.3.bb => libsodium_1.0.8.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-oe/recipes-support/libsodium/{libsodium_1.0.3.bb =>
libsodium_1.0.8.bb} (65%)
diff --git
Many failures are caused by change to default EXTRA_OEMAKE. Couple fixes
were already sent for oe-core an meta-oe layers, so hopefully next
report will be more useful.
The list of failures is probably much longer, a lot of them aren't shown
because the dependencies weren't built so only few
This release includes support for Ne10 to improve performance on ARM NEON
capable CPUs. Also, packageconfigs are introduced for controlling whether
Opus uses fixed or floating point processing and whether or not fast
floating point approximations are enabled.
Signed-off-by: Carlos Rafael Giani
This release includes support for Ne10 to improve performance on ARM NEON
capable CPUs. Also, packageconfigs are introduced for controlling whether
Opus uses fixed or floating point processing and whether or not fast
floating point approximations are enabled.
libopus-fpu.inc wasn't doing much,
thanks for doing it Mike.
On Mon, Feb 8, 2016 at 2:57 AM, Mike Crowe wrote:
> This series fixes various recipes that rely on the current default
> value of EXTRA_OEMAKE = "-e MAKEFLAGS=" to explicitly set that value
> in the hope that bitbake.conf can set EXTRA_OEMAKE = "" in
Signed-off-by: Andrea Adami
---
...inux-yocto-tiny-kexecboot_4.1.bb => linux-yocto-tiny-kexecboot_4.4.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta-initramfs/recipes-kernel/linux/{linux-yocto-tiny-kexecboot_4.1.bb
=>
Hi,
This patch fixes bluetooth.h strict C compilation error when building
bluez4 in fido branch.
thanks
Ankur
Signed-off-by: Ankur Tyagi
---
.../strict-C-compilation-error-fix.patch | 42
++
Keeping debian packaging-style we have a copy of klibc-xxx.so in libklibc-dev.
Wile there silence the warning about it being already stripped.
NOTE: klcc in OE is used as cross-compiler so the packaging is tweaked and
there is no /bin/klcc for target (drifting from debian).
Signed-off-by:
26 matches
Mail list logo