From: Christopher Larson chris_lar...@mentor.com
Currently, command.py can return an error message from runCommand, due to
being unable to run the command, yet few of our UIs (just hob) can handle it
today. This can result in seeing a TypeError with traceback in certain rare
circumstances.
To
Along the lines of the oe classic patch I propose to split as follows:
mtd-utils-jffs2 package containing
jffs2dump
jffs2reader
mkfs.jffs2
mtd-utils-ubifs package containing:
mkfs.ubifs
ubiattach
ubicrc32
ubidetach
ubiformat
ubimkvol
ubinfo
ubinize
ubirename
ubirmvol
ubirsvol
ubiupdatevol
2013/1/11 Eric Bénard e...@eukrea.com
Hi Frans,
[...]
IIRC sumtol is used for jffs2 images (to create the erase block
summary) so that may better fit into mtd-utils-jffs2
Also, nftl* rfd* doc* ftl* serve_image may go into a separate packate
(mtd-utils-misc ?) as I believe those tools are
Hi Frans,
Le Fri, 11 Jan 2013 09:40:43 +0100,
Frans Meulenbroeks fransmeulenbro...@gmail.com a écrit :
Along the lines of the oe classic patch I propose to split as follows:
mtd-utils-jffs2 package containing
jffs2dump
jffs2reader
mkfs.jffs2
mtd-utils-ubifs package containing:
On 01/11/2013 02:31 AM, Yi Qingliang wrote:
when compiling using 4 threads, I got following error.
the glib2.0-native want find dbus header file.
If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.
when grep glib2.0 bb files, I can't find dbus in dependency, why?
Hi,
What's the
On 10 January 2013 23:59, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
Please don't use qemu, use something like qemuall or allqemu since I
have some thoughts about how this might interact with the qemu class,
most involving the word badly ;-).
That was my fault, I thought it was
On Thu, Jan 10, 2013 at 11:52:29PM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: 5de138939c42b0a6d80732130b2617fd60a7d545
URL:
http://git.openembedded.org/?p=openembedded-core.gita=commit;h=5de138939c42b0a6d80732130b2617fd60a7d545
Author:
For qemu machines, connman should not configure
virtual wired interfaces. Wired interfaces (eth0)
are assigned static IP addresses by the virtual machine
manager (qemu). This packages places the eth0 interface in
a list of blacklisted interfaces, forbiding connman
administering wired interfaces
This set of patches will:
- update connman to 1.10
- solve the issue of lost connectivity with qemu machines
connman will clear previous configuration for a network
interface, rendering qemu machines eth0 unusable, because
there is no DHCP server to be used, and the static
On Fri, Jan 11, 2013 at 12:53:38PM +0200, Cristian Iorga wrote:
For qemu machines, connman should not configure
virtual wired interfaces. Wired interfaces (eth0)
are assigned static IP addresses by the virtual machine
manager (qemu). This packages places the eth0 interface in
a list of
Yes, I think I missed that. Should I resend the patches?
-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Friday, January 11, 2013 1:28 PM
To: Iorga, Cristian
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V3 2/2] connman-conf:
Cristian Iorga cristian.iorga-ral2jqcrhueavxtiumw...@public.gmane.org
writes:
For qemu machines, connman should not configure virtual wired interfaces.
This is not a qemu-only problem but affects all platforms with nfs
rootfs, isn't it?
Setup whether to disable configuration of interface
Hello Enrico, see my answers below.
Regards,
Cristian
-Original Message-
From: Enrico Scholz [mailto:enrico.sch...@sigma-chemnitz.de]
Sent: Friday, January 11, 2013 2:23 PM
To: openembedded-core@lists.openembedded.org
Cc: Cristian Iorga
Subject: Re: [PATCH V3 2/2] connman-conf:
- this allows the creation of a SDK containing all the needed
libraries to develop QT4 for X applications
- the recipes were factorized to share as much code as possible
- binaries generated using the toolchain were run tested on an
ARMv7 target
- both qt qte toolchains were build tested for
else for example meta-toolchain-qte.bb is also ignored.
Signed-off-by: Eric Bénard e...@eukrea.com
---
.gitignore |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/.gitignore b/.gitignore
index a2141f0..6ece6b8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,7 +7,7 @@
On Thu, Jan 10, 2013 at 11:27 PM, Martin Ertsaas marti...@gmail.com wrote:
On 01/10/13 15:15, Chris Larson wrote:
On Thu, Jan 10, 2013 at 1:50 AM, Martin Ertsaas marti...@gmail.comwrote:
On mac, os.unlink can not be done to remove directories, and so we have to
explicitly use
On 01/10/2013 08:27 PM, Khem Raj wrote:
On Thu, Jan 10, 2013 at 12:02 AM, Radu Moisan radu.moi...@intel.com wrote:
On 01/09/2013 07:14 PM, Khem Raj wrote:
On Tue, Jan 8, 2013 at 4:24 AM, Radu Moisan radu.moi...@intel.com wrote:
As Ross suggested I've done the following changes to the
On Thu, 2013-01-10 at 23:59 +, Richard Purdie wrote:
On Thu, 2013-01-10 at 20:26 +, Burton, Ross wrote:
On 10 January 2013 18:42, Cristian Iorga cristian.io...@intel.com wrote:
0002-storage.c-If-there-is-no-d_type-support-use-fstatat.patch
- adapted to the new version
On Wed, 2013-01-09 at 11:00 +0200, Constantin Musca wrote:
- add a task to setup multilib configuration for target gcc
- this commit adapts Nitin Kamble's work to gcc 4.7
Tests:
root@qemux86-64:~# gcc -m64 t.c -o t
root@qemux86-64:~# file t
t: ELF 64-bit LSB executable, x86-64, version 1
On Fri, 2013-01-11 at 15:20 +, Richard Purdie wrote:
On Wed, 2013-01-09 at 11:00 +0200, Constantin Musca wrote:
- add a task to setup multilib configuration for target gcc
- this commit adapts Nitin Kamble's work to gcc 4.7
Tests:
root@qemux86-64:~# gcc -m64 t.c -o t
When building world which takes long time to finish I
sometimes see bitbake hanging forever. It didn't happen
until I've enabled PR Service. But maybe it's not caused
by PR Service and it's just coincidence.
I've to kill python processes manually and this traceback shown:
Exception in thread
Hello Richard, Saul,
Which versions of connman upgrade patches were used? V2 or V3?
Also, does the issue will be present with V3 also?
Regards,
Cristian
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org]
License file changed the year,
triggering a change in checksum
Signed-off-by: Cristian Iorga cristian.io...@intel.com
---
meta/recipes-support/db/{db_5.3.15.bb = db_5.3.21.bb} |8
1 file changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-support/db/{db_5.3.15.bb =
Signed-off-by: Cristian Iorga cristian.io...@intel.com
---
meta/recipes-extended/quota/{quota_4.00.bb = quota_4.01.bb} |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/quota/{quota_4.00.bb = quota_4.01.bb} (85%)
diff --git
On 1/11/13 10:18 AM, Cristian Iorga wrote:
License file changed the year,
triggering a change in checksum
Any change is BerkleyDB versions requires us to verify RPM and Smart
functionality. I don't have any objections to the change -- just pointing that out.
--Mark
Signed-off-by:
Noted. Thanks, I will do that on Monday.
Regards,
Cristian
-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Mark
Hatle
Sent: Friday, January 11, 2013 6:36 PM
To:
On 01/11/2013 07:12 AM, Radu Moisan wrote:
On 01/10/2013 08:27 PM, Khem Raj wrote:
On Thu, Jan 10, 2013 at 12:02 AM, Radu Moisan radu.moi...@intel.com
wrote:
On 01/09/2013 07:14 PM, Khem Raj wrote:
On Tue, Jan 8, 2013 at 4:24 AM, Radu Moisan radu.moi...@intel.com
wrote:
As Ross suggested
On 01/11/2013 07:35 AM, Iorga, Cristian wrote:
Hello Richard, Saul,
Which versions of connman upgrade patches were used? V2 or V3?
I used the V2 version since that what I had available, I wanted to get a
sanity run it for that and the gcc multilib changes (which also broke
gcc-runtime).
Richard,
Another batch of automake related changes from Marko (Thanks Marko!)
Along with some other fixes and patches, I have again included the
cairo patch as I am not sure what your objection to it is.
Sau!
The following changes since commit 1e63a3b7b7915d40bb59976a02b9f53968997ed3:
From: Tom Zanussi tom.zanu...@intel.com
recipes-kernel/lttng/lttng-ust was removed by a previous patch, which
also removed the naming conflict that caused the lttng-2.0 version of
lttng-ust to be named lttng2-ust. lttng2-ust was the only lttng-2.0
recipe to be named in this way and since that
From: Tom Zanussi tom.zanu...@intel.com
'legacy' lttng was removed, so we need to remove the references to
the legacy lttng recipes, namely lttng-control and lttng-viewer.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-yocto/conf/distro/include/distro_alias.inc | 2 --
From: Tom Zanussi tom.zanu...@intel.com
This patchset removes legacy lttng, which hasn't been operational in
Yocto for awhile now. lttng-2.0 is the current version, which was
recently updated and now does work.
With legacy lttng gone, lttng-2.0 can be renamed back to lttng, which
this patchset
From: Tom Zanussi tom.zanu...@intel.com
recipes-kernel/lttng was removed by a previous patch, which also
removed the naming conflict that caused the lttng-2.0 version of lttng
to be named recipes-kernel/lttng-2.0. Since the naming conflict has
disappeared, we can go back to the simpler naming.
From: Tom Zanussi tom.zanu...@intel.com
Add entries for the new lttng-2.0 recipes lttng-modules, lttng-tools,
and babeltrace, to maintain consistency.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-yocto/conf/distro/include/recipe_color.inc | 3 +++
1 file changed, 3 insertions(+)
ack
*Andrei Gherzan*
mobile +40.744.478.414 fax +40.31.816.28.12
Email: and...@gherzan.ro
Email: andrei.gher...@windriver.com
Romania
On Thu, Jan 10, 2013 at 9:01 AM, Florin Sarbu florin.sa...@windriver.comwrote:
alsa-utils-alsaconf rpm contains the bash script alsaconf. In order
to have
On 01/11/2013 11:20 AM, tom.zanu...@intel.com wrote:
From: Tom Zanussi tom.zanu...@intel.com
recipes-kernel/lttng/lttng-ust was removed by a previous patch, which
also removed the naming conflict that caused the lttng-2.0 version of
lttng-ust to be named lttng2-ust. lttng2-ust was the only
On 01/11/2013 11:20 AM, tom.zanu...@intel.com wrote:
From: Tom Zanussi tom.zanu...@intel.com
This patchset removes legacy lttng, which hasn't been operational in
Yocto for awhile now. lttng-2.0 is the current version, which was
recently updated and now does work.
With legacy lttng gone,
xz contains a GPLv3 m4 macro which is used at build time, this does not make
the installed or runtime items GPLv3, which is what the LICESNE field pertains
to, therefor remove it from the LICENSE field.
Signed-off-by: Saul Wold s...@linux.intel.com
---
meta/recipes-extended/xz/xz_5.1.2alpha.bb |
On 01/08/2013 04:24 AM, Radu Moisan wrote:
As Ross suggested I've done the following changes to the previous set:
* added two patches (the first two) that address multiple init systems support,\
as in shifting from default hardcoded sysvinit to something more generic while
the default values
From: Tom Zanussi tom.zanu...@intel.com
This patchset removes legacy lttng, which hasn't been operational in
Yocto for awhile now. lttng-2.0 is the current version, which was
recently updated and now does work.
With legacy lttng gone, lttng-2.0 can be renamed back to lttng, which
this patchset
From: Tom Zanussi tom.zanu...@intel.com
recipes-kernel/lttng was removed by a previous patch, which also
removed the naming conflict that caused the lttng-2.0 version of lttng
to be named recipes-kernel/lttng-2.0. Since the naming conflict has
disappeared, we can go back to the simpler naming.
From: Tom Zanussi tom.zanu...@intel.com
This removes 'legacy' lttng - it hasn't actually worked for awhile
now, and has been replaced by equivalent functionality in
recipes-kernel/lttng-2.0 (which will be renamed to lttng in a
follow-up patch).
Fixes [YOCTO #3303].
Signed-off-by: Tom Zanussi
From: Tom Zanussi tom.zanu...@intel.com
recipes-kernel/lttng/lttng-ust was removed by a previous patch, which
also removed the naming conflict that caused the lttng-2.0 version of
lttng-ust to be named lttng2-ust. lttng2-ust was the only lttng-2.0
recipe to be named in this way and since that
On 01/07/2013 06:22 PM, ChenQi wrote:
On 01/07/2013 06:30 PM, Otavio Salvador wrote:
On Mon, Jan 7, 2013 at 1:06 AM, ChenQi qi.c...@windriver.com wrote:
On 01/07/2013 03:05 AM, Otavio Salvador wrote:
On Sun, Jan 6, 2013 at 7:44 AM, qi.c...@windriver.com wrote:
From: Chen Qi
On 01/06/2013 01:44 AM, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
read_only_rootfs_hook: this funtion is invoked only if 'read-only-rootfs'
is in IMAGE_FEATURES. It tweaks some basic files and makes populate-
volatile.sh script run at rootfs time.
choose_volatile_conf:
On Friday, January 11, 2013 05:30:55 PM ChenQi wrote:
On 01/11/2013 02:31 AM, Yi Qingliang wrote:
when compiling using 4 threads, I got following error.
the glib2.0-native want find dbus header file.
If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.
when grep glib2.0 bb
46 matches
Mail list logo
