ping
-Roy
On 2015年08月27日 09:18, Rongqing Li wrote:
On 2015年08月26日 18:16, Burton, Ross wrote:
On 26 August 2015 at 06:58, mailto:rongqing...@windriver.com>> wrote:
+export PYTHON_SITEPACKAGES_DIR
Why do you export this and then use \$(PYTHON_SITEPACKAGES_DIR), isn't
just using ${PYTHO
On 09/07/2015 10:08 PM, Burton, Ross wrote:
On 7 September 2015 at 03:19, mailto:wenzong@windriver.com>> wrote:
+ > Note on targets where the @ character is the start of a comment
+ > (eg ARM) then another character is used instead. For example the
+ > ARM port uses the % cha
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: Friday, September 04, 2015 10:33 PM
> To: Slater, Joseph
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [oe-core][PATCH 1/1] busybox: more nails in the coffin
>
> On F
From: Armin Kuster
three security fixes.
Signed-off-by: Armin Kuster
---
.../bind/bind/CVE-2015-1349.patch | 60 +++
.../bind/bind/CVE-2015-4620.patch | 36 ++
.../bind/bind/CVE-2015-5722.patch | 490 +
meta/recipes-conne
On Mon, 2015-09-07 at 14:15 -0700, Khem Raj wrote:
> > On Sep 7, 2015, at 12:36 PM, Phil Blundell wrote:
> >
> > On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
> >> update-rc.d is now needed by systemd to interact with sysv
> >> scripts, so if we have a mixed system, then we can not uninstall
> On Sep 7, 2015, at 12:36 PM, Phil Blundell wrote:
>
> On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
>> update-rc.d is now needed by systemd to interact with sysv
>> scripts, so if we have a mixed system, then we can not uninstall
>> update-rc.d as it is going to break systemd functionalit
On Mon, 2015-09-07 at 14:12 -0700, Khem Raj wrote:
> > On Sep 7, 2015, at 2:09 PM, Richard Purdie
> > wrote:
> >
> > On Mon, 2015-09-07 at 14:00 -0700, Khem Raj wrote:
> >>> On Sep 7, 2015, at 1:56 PM, Richard Purdie
> >>> wrote:
> >>>
> >>> A "bitbake core-image-sato -c testimage" replicated
> On Sep 7, 2015, at 2:09 PM, Richard Purdie
> wrote:
>
> On Mon, 2015-09-07 at 14:00 -0700, Khem Raj wrote:
>>> On Sep 7, 2015, at 1:56 PM, Richard Purdie
>>> wrote:
>>>
>>> A "bitbake core-image-sato -c testimage" replicated it here FWIW, have
>>> you tried testimage to see if that somehow
On Mon, 2015-09-07 at 14:00 -0700, Khem Raj wrote:
> > On Sep 7, 2015, at 1:56 PM, Richard Purdie
> > wrote:
> >
> > A "bitbake core-image-sato -c testimage" replicated it here FWIW, have
> > you tried testimage to see if that somehow makes a difference? Shoudn't
> > be hard to test with that an
> On Sep 7, 2015, at 1:56 PM, Richard Purdie
> wrote:
>
> A "bitbake core-image-sato -c testimage" replicated it here FWIW, have
> you tried testimage to see if that somehow makes a difference? Shoudn't
> be hard to test with that and for sato, it should run pretty quickly.
>
> It all works wi
On Mon, 2015-09-07 at 13:53 -0700, Khem Raj wrote:
> > On Sep 7, 2015, at 12:26 PM, Richard Purdie
> > wrote:
> >
> > On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
> >> Changes Since last time
> >> - Now that 225 is out upgrade recipe to 225, changes between 224 and 225
> >> are minor
> >>
> On Sep 7, 2015, at 12:26 PM, Richard Purdie
> wrote:
>
> On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
>> Changes Since last time
>> - Now that 225 is out upgrade recipe to 225, changes between 224 and 225 are
>> minor
>> but fixes in networkd are important
>> - Implement systemd-sysv-
On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
> update-rc.d is now needed by systemd to interact with sysv
> scripts, so if we have a mixed system, then we can not uninstall
> update-rc.d as it is going to break systemd functionality
The description above implies that you will only uninstall
On Sun, 2015-09-06 at 15:25 +, Khem Raj wrote:
> Changes Since last time
> - Now that 225 is out upgrade recipe to 225, changes between 224 and 225 are
> minor
> but fixes in networkd are important
> - Implement systemd-sysv-install for OE
> - Enable getopt in busybox needed for systemd-sysv
Currently if this fails you see:
"AssertionError: 1 != 0"
which is useless. Add the output of the failed command so we can stand
some chance of debugging what went wrong.
Signed-off-by: Richard Purdie
diff --git a/meta/lib/oeqa/selftest/sstatetests.py
b/meta/lib/oeqa/selftest/sstatetests.py
i
fixes two secruity issues:
CVE-2015-5722 and CVE-2015-5986.
see release notes for more information.
ftp://ftp.isc.org/isc/bind9/9.10.2-P4/RELEASE-NOTES.bind-9.10.2-P4.html
Signed-off-by: Armin Kuster
---
.../bind/{bind_9.10.2-P3.bb => bind_9.10.2-P4.bb} | 4 ++--
1 file chan
On 07-09-15 13:56, Jussi Kukkonen wrote:
On 7 September 2015 at 13:14, Mike Looijmans mailto:mike.looijm...@topic.nl>> wrote:
Just sped another hour or so trying to pinpoint this, but I cannot
wrap my head around it. What do I have to do to add a license to a
layer without these anno
[YOCTO #7898]
[YOCTO #7761]
[YOCTO #7804]
Signed-off-by: Cristina Agurida
---
meta/lib/oeqa/runtime/parselogs.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/lib/oeqa/runtime/parselogs.py
b/meta/lib/oeqa/runtime/parselogs.py
index ed43510..e20947b 100644
--- a/meta/lib/oeqa/ru
On Fri, 2015-09-04 at 17:16 -0500, Peter Seebach wrote:
> Pseudo 1.7 adds an experimental feature (which I think needs more testing
> before it becomes the default) allowing the pseudo client to store modes
> and uid/gid values in extended attributes rather than using the sqlite
> database. On most
On Mon, Sep 07, 2015 at 12:37:35PM +0300, Alexander Kanavin wrote:
> On 09/04/2015 05:16 PM, Khem Raj wrote:
>
> > I will send these patches only when oe-core is updated. Recipe
> > moving is always controversial, and I don't want to cause confusion
> > when the change is accepted by o
Hi,
Ty for the review.
Related to your comments I will move those two issues to common errors.
BR,
Cristina Agurida
QA CW Validation Engineer
Phone: +40768855744
SSD Open Source Technology Center
Bucharest, Romania
George Constantinescu street, 3, Entrance C, Floor 4, ZIP: 020339
From: Jussi Kukk
If a task shows an error, the full log is surpressed since bitbake assumes
the user has been shown what is wrong. In this code path that isn't the
case and its much more helpful to show the user the full error. Therefore
show a warning instead to aid usability.
Signed-off-by: Richard Purdie
diff
The smc91c111.c driver appears to have several issues. The can_receive()
function can return that the driver is ready when rx_fifo has not been
freed yet. There is also no sanity check of rx_fifo() in _receive() which
can lead to corruption of the rx_fifo array.
release_packet() can also call qem
On Mon, Sep 7, 2015 at 7:08 AM, Steffen Sledz wrote:
> On 07.09.2015 09:09, Steffen Sledz wrote:
> > On 05.09.2015 13:29, Mike Looijmans wrote:
> >> ... and I think the u-boot recipe recently learned to have multiple
> targets, so you can build multiple bootloaders for a single machine too.
> >
>
On 6 September 2015 at 09:12, Robert Yang wrote:
> Ping.
>
A similar but more basic (just adding util-linux as a build dep) patch was
merged as c158cdd. If you want it to be a packageconfig then please rebase.
Ross
--
___
Openembedded-core mailing l
On 7 September 2015 at 15:15, Phil Blundell wrote:
> Surely the ARM assembly code would never have worked on x86 anyway. It's
> a bit of a mystery how the original code ever worked for anyone on ARM,
> given that binutils has behaved this way for nearly 20 years, but this
> patch does seem like
On Mon, 2015-09-07 at 15:08 +0100, Burton, Ross wrote:
>
>
> On 7 September 2015 at 03:19, wrote:
>
> + > Note on targets where the @ character is the start of a
> comment
> + > (eg ARM) then another character is used instead. For
> example the
> + > A
On 7 September 2015 at 03:19, wrote:
> + > Note on targets where the @ character is the start of a comment
> + > (eg ARM) then another character is used instead. For example the
> + > ARM port uses the % character.
>
Is the documentation badly written or does this now broke the build on x86?
From: "qi.c...@windriver.com"
Add a script to publish an extensible SDK that has previously been built
to a specified destination. This published SDK is intended to be
accessed by the devtool sdk-update command from an installed copy of the
extensible SDK.
e.g.
oe-publish-sdk
Signed-off-by: C
From: "qi.c...@windriver.com"
The previous code assumes that bitbake/ directory is under the core layer.
This is the case for Yocto project. But users might clone oe-core and bitbake
separately. So we use bb.__file__ to locate the bitbake directory to make sure
it's copied into the extensible SDK
From: "qi.c...@windriver.com"
Enable updating the installed extensible SDK from a local or remote
server, avoiding the need to install it again from scratch when
updating. (This assumes that the updated SDK has been built and then
published somewhere using the oe-publish-sdk script beforehand.)
From: "qi.c...@windriver.com"
These dependencies were deliberately removed because it was assumed that
they were provided by nativesdk packages. On the one hand, nativesdk packages
in extensible SDK don't have these packages; on the other hand, even if we
add these nativesdk packages, they are st
From: "qi.c...@windriver.com"
When publishing SDK, what we want is basically its metadata and sstate
cache objects. We don't want the SDK to be prepared with running bitbake
as it takes time which reproduces meaningless output for the published SDK.
So this patch adds an option to allow for SDK
From: "qi.c...@windriver.com"
Copy the contents of local.conf under TOPDIR into the final generated
local.conf. In this way, custom settings are also made into the final
local.conf like IMAGE_INSTALL, DISTRO_FEATURES, VIRTUAL-RUNTIME_xxx,
etc. Comments and blank lines are filtered out.
Before th
This rolls up a set of previously posted patches from Qi and Brendan
with some changes from me.
Changes since the previously posted versions:
* populate_sdk_ext: install the latest buildtools-tarball:
- Avoid poky-specific path usage
* populate_sdk_ext: consider custom configuration in local.co
From: Brendan Le Foll
Signed-off-by: Brendan Le Foll
---
meta/files/toolchain-shar-extract.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/files/toolchain-shar-extract.sh
b/meta/files/toolchain-shar-extract.sh
index 27a1607..3624940 100644
--- a/meta/files/toolcha
From: "qi.c...@windriver.com"
If we do `bitbake buildtools-tarball' and then after one day do `bitbake
core-image-minimal -c populate_sdk_ext', we would meet errors like below.
| install: cannot stat '/buildarea2/chenqi/poky/build-systemd/tmp/deploy/sdk/
poky-glibc-x86_64-buildtools-tarball-core
Only poky sets SDK_NAME to include ${IMAGE_BASENAME} (i.e. ${PN}), so we
can't assume the buildtools filename will include it here. Change it to
look for a file with "buildtools-nativesdk-standalone" in the name
(the buildtools-tarball recipe itself sets TOOLCHAIN_OUTPUTNAME to
include this.)
Sign
From: Brendan Le Foll
Extensible SDK cannot be installed as root so by default offer to install it in
user's home directory under distro/distro_version replacing the normal SDK
version '+' char with a '_' as that's a restricted character for bitbake
Signed-off-by: Brendan Le Foll
Signed-off-by:
From: Brendan Le Foll
There are some characters that cannot appear in the installation path, so we
need to check for these
Signed-off-by: Brendan Le Foll
Signed-off-by: Paul Eggleton
---
meta/files/toolchain-shar-extract.sh | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-
On 07.09.2015 09:09, Steffen Sledz wrote:
> On 05.09.2015 13:29, Mike Looijmans wrote:
>> ... and I think the u-boot recipe recently learned to have multiple targets,
>> so you can build multiple bootloaders for a single machine too.
>
> That sounds great. Can someone give a pointer to some docum
On 7 September 2015 at 13:14, Mike Looijmans
wrote:
> Just sped another hour or so trying to pinpoint this, but I cannot wrap my
> head around it. What do I have to do to add a license to a layer without
> these annoying warnings?
I just tried this (with master branch) and it seems to work fine
On 8 September 2015 at 14:51, Cristina Agurida <
cristina-danielax.agur...@intel.com> wrote:
> [YOCTO #7898]
> [YOCTO #7760]
> [YOCTO #7761]
> [YOCTO #7804]
>
> Signed-off-by: Cristina Agurida
> ---
> meta/lib/oeqa/runtime/parselogs.py | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --
[YOCTO #7898]
[YOCTO #7760]
[YOCTO #7761]
[YOCTO #7804]
Signed-off-by: Cristina Agurida
---
meta/lib/oeqa/runtime/parselogs.py | 9 +
1 file changed, 9 insertions(+)
diff --git a/meta/lib/oeqa/runtime/parselogs.py
b/meta/lib/oeqa/runtime/parselogs.py
index ed43510..367ee6d 100644
--- a
Just sped another hour or so trying to pinpoint this, but I cannot wrap my
head around it. What do I have to do to add a license to a layer without these
annoying warnings?
Mike.
On 03-07-15 09:23, Mike Looijmans wrote:
In my layer.conf I have:
LICENSE_PATH += "${LAYERDIR}/licenses"
In t
Wic uses bitbake variable ROOTFS_SIZE to set correspondent
partition size. This variable is a literal representing
float value. Wic crashes trying to convert it to int with
the error: invalid literal for int() with base 10: '10166.0'
Fixed this by converting variable to float and rounding result.
Note that I copied and tweaked the ppc (32 bit) configuration and
didn't in any way test this with qemu; I only wanted
a working configuration for testing ppc64 builds using poky.
But it could be a starting point.
Signed-off-by: Alexander Kanavin
---
meta/conf/machine/qemuppc64.conf | 11 +++
On 09/04/2015 05:16 PM, Khem Raj wrote:
I will send these patches only when oe-core is updated. Recipe
moving is always controversial, and I don't want to cause confusion
when the change is accepted by one side and rejected by the other.
On the contrary you can make a note in patch
On 05.09.2015 13:29, Mike Looijmans wrote:
> ... and I think the u-boot recipe recently learned to have multiple targets,
> so you can build multiple bootloaders for a single machine too.
That sounds great. Can someone give a pointer to some documentation or examples
for that?
--
DResearch Fah
49 matches
Mail list logo
