From: Alexandru Moise
If an SSL/TLS server or client is running on a 32-bit host, and a
specific cipher is being used, then a truncated packet can cause that
server or client to perform an out-of-bounds read, usually resulting
in a crash.
Backported from:
From: Yi Zhao
There is a carry propagating bug in the Broadwell-specific Montgomery
multiplication procedure that handles input lengths divisible by, but
longer than 256 bits.
External References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055
From: "Chang, Rebecca Swee Fun"
The previous version of ed-1.14.1 no longer exist in upstream source
archive at https://ftp.gnu.org/gnu/ed/. Upstream version was being
replaced by a brand new version.
Updated version to build and tarball checksums.
[YOCTO
From: Chang Rebecca Swee Fun
This work has been similar to [YOCTO #11389] but this is mainly on
devtool 'upgrade' subcommand. This feature is important for devtool
as this will surely improve the usability of devtool and improve the
quality of the recipe being
From: Chang Rebecca Swee Fun
When devtool upgrade is run on a recipe with revision specified
that is not on master branch, and branch isn't set by --srcbranch or -B,
then we should get the correct branch and append the branch to the URL.
If the revision was
From: Chang Rebecca Swee Fun
Rework on PATCHv2.
addtask do_prepare_recipe_sysroot is having the same effect on building
more dependencies for devshell.
The 2nd patch in series is to clean up some trailing whitespaces within
devshell.bbclass.
I have done some
From: Chang Rebecca Swee Fun
Hi,
The following warning occurs when building zephyr with arduino-101-sss.
WARNING:
/srv/sdc/builds/11319/meta/recipes-extended/ghostscript/ghostscript_9.20.bb:
Unable to get checksum for ghostscript SRC_URI entry objarch.h:
From: Chang Rebecca Swee Fun
The following warning occurs when building with meta-zephyr
with MACHINE set to arduino-101-sss:
WARNING:
/srv/sdc/builds/11319/meta/recipes-extended/ghostscript/ghostscript_9.20.bb:
Unable to get checksum for ghostscript SRC_URI
From: Chang Rebecca Swee Fun
Use the scriptpath module in order to standardize the adding of
bitbake and meta/lib path to sys.path.
Signed-off-by: Chang Rebecca Swee Fun
---
scripts/wic | 7 +++
1 file changed, 3
From: Chang Rebecca Swee Fun
Hi all,
As the subject called out: this patch series enable wic in eSDK.
The details of what I have done are documented within the commit message.
Basically wic requires an OE build environment, but we are using a
different
From: Chang Rebecca Swee Fun
wic needs a set of tools to be available from sysroots.
wic will find bitbake executable within the environment,
and wic was unable to locate bitbake executable within eSDK
because it wasn't setup with the OE build environment
From: Chang Rebecca Swee Fun
When we run wic within eSDK:
$ wic create mkefidisk -e core-image-minimal
ERROR: BUILDDIR not found, exiting. (Did you forget to source
oe-init-build-env?)
In order to figure out variable values, one must have sourced
the OE build
From: Chang Rebecca Swee Fun
wic modules in scripts/lib/ are needed for wic to work, but path to
the python module is not exported in eSDK environment and we were
using an absolutized path of wic script within the sysroots.
We now changed to use real script
From: Chang Rebecca Swee Fun
Make 'wic' image creation tool/command available in eSDK
environment. This would allow eSDK users to manipulate
images within eSDK environment.
[YOCTO #12177]
Signed-off-by: Chang Rebecca Swee Fun
From: Chang Rebecca Swee Fun
When we run wic within eSDK:
$ wic create mkefidisk -e core-image-minimal
ERROR: BUILDDIR not found, exiting. (Did you forget to source
oe-init-build-env?)
In order to figure out variable values, one must have sourced
the OE build
From: Chang Rebecca Swee Fun
wic modules in scripts/lib/ are needed for wic to work, but path to
the python module is not exported in eSDK environment and we were
using an absolutized path of wic script within the sysroots.
We now changed to use real script
From: Chang Rebecca Swee Fun
Make 'wic' image creation tool/command available in eSDK
environment. This would allow eSDK users to manipulate
images within eSDK environment.
[YOCTO #12177]
Signed-off-by: Chang Rebecca Swee Fun
From: Chang Rebecca Swee Fun
wic needs a set of tools to be available from sysroots.
wic will find bitbake executable within the environment,
and wic was unable to locate bitbake executable within eSDK
because it wasn't setup with the OE build environment
From: Chang Rebecca Swee Fun
Use the scriptpath module in order to standardize the adding of
bitbake and meta/lib path to sys.path.
Signed-off-by: Chang Rebecca Swee Fun
---
scripts/wic | 7 +++
1 file changed, 3
From: Chang Rebecca Swee Fun
Hi all,
Resend as v2 as I realized an issue with BUILDDIR being set
was not correct. I made the correction on Patch 4 by setting
BUILDDIR to sdkroot variable (eSDK base path) before we alter
the variable for bitbake executable file
From: Chang Rebecca Swee Fun
Tarball sources can be checksummed and are faster to download.
Signed-off-by: Chang Rebecca Swee Fun
---
meta/recipes-support/bmap-tools/bmap-tools_3.4.bb | 6 +++---
1 file changed, 3
From: Chang Rebecca Swee Fun
Tarball sources can be checksummed and are faster to download.
Added UPSTREAM_CHECK_URI to improve recipe maintenance and to
verify upstream version check is still work.
Signed-off-by: Chang Rebecca Swee Fun
22 matches
Mail list logo