We have found a problem with upgrading packages on our own image.
(Hopefully it'll show up to an error from our side).
After upgrading system packages, like busybox, we render our system
unusable... In the busybox case, all symlinks pointing to busybox has
been removed, and not reinstated during
On Fri, 2011-11-04 at 17:07 +0100, Martin Jansa wrote:
On Fri, Nov 04, 2011 at 11:57:46AM -0400, Robert P. J. Day wrote:
stumbled over this so i did a more thorough search:
$ grep -w PARALLEL_MAKE $(find . -name *.bb)
./meta/recipes-qt/qt-apps/qmmp_0.5.1.bb:PARALLEL_MAKE =
From: Tom Zanussi tom.zanu...@intel.com
Have sugarbay make use of the new corei7-specific tune file.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-sugarbay/conf/machine/sugarbay.conf |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
From: Tom Zanussi tom.zanu...@intel.com
Have jasperforest make use of the new corei7-specific tune file.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-jasperforest/conf/machine/jasperforest.conf |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: Tom Zanussi tom.zanu...@intel.com
Have fri2 use more power-friendly settings.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/cfg/kernel-cache/bsp/fri2/fri2.scc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta/cfg/kernel-cache/bsp/fri2/fri2.scc
From: Tom Zanussi tom.zanu...@intel.com
Have jasperforest use more power-friendly settings.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../kernel-cache/bsp/jasperforest/jasperforest.scc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
From: Tom Zanussi tom.zanu...@intel.com
The fishriver reference board has HPET hardware - enable it.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
current poky ref manual seems pretty adamant about need for
LIC_FILES_CHKSUM:
Note that this variable is mandatory for all recipes, unless the
LICENSE variable is set to CLOSED.
but there's at least one counter-example,
meta-demoapps/recipes-graphics/pong-clock/pong-clock_1.0.bb:
=
On 11/7/11 10:01 AM, Robert P. J. Day wrote:
current poky ref manual seems pretty adamant about need for
LIC_FILES_CHKSUM:
Note that this variable is mandatory for all recipes, unless the
LICENSE variable is set to CLOSED.
but there's at least one counter-example,
On 11/7/11 10:24 AM, Robert P. J. Day wrote:
On Mon, 7 Nov 2011, Mark Hatle wrote:
On 11/7/11 10:01 AM, Robert P. J. Day wrote:
current poky ref manual seems pretty adamant about need for
LIC_FILES_CHKSUM:
Note that this variable is mandatory for all recipes, unless the
LICENSE
On Mon, 7 Nov 2011, Mark Hatle wrote:
On 11/7/11 10:01 AM, Robert P. J. Day wrote:
current poky ref manual seems pretty adamant about need for
LIC_FILES_CHKSUM:
Note that this variable is mandatory for all recipes, unless the
LICENSE variable is set to CLOSED.
but there's at
On 11-11-07 10:56 AM, tom.zanu...@intel.com wrote:
From: Tom Zanussitom.zanu...@intel.com
This just finishes up the previous set of meta-intel cleanups. All
machines were build- and run-tested.
Please pull into linux-yocto-3.0 and linux-yocto-dev.
The following changes since commit
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
all of the atom pc info is already in that file, all that was
missing was the entry for it in the early list.
diff --git a/README.hardware b/README.hardware
index d4f7b47..462e6d1 100644
--- a/README.hardware
+++ b/README.hardware
@@
Robert's emails about recipes in meta-demoapps missing LIC_FILES_CHKSUM
made me realize that for my documentation audit runs, I'm only using the
default layers Poky gives you when you source the build environment script.
Shall I change this to include all meta- layers we ship with? This would
On Monday 07 November 2011 12:35:02 Robert P. J. Day wrote:
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
all of the atom pc info is already in that file, all that was
missing was the entry for it in the early list.
diff --git a/README.hardware b/README.hardware
index
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh)
* Yocto 1.2 planning and M1 Status - 10 min (Song)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_1.2_Schedule
* Opens - 10 min
* Action
I approach embedded Linux from a path of taking a Distro like Ubuntu or
Fedora and chopping it down to a working set of code that forms the final
solution. Obviously, not the same methology as Yocto. With some success
with the current methods, it's difficult to see the advantages of Yocto.
I'm
On 2011-11-07 14:59, James Abernathy wrote:
I approach embedded Linux from a path of taking a Distro like Ubuntu or Fedora
and chopping it down to a working set of code that forms the final solution.
Obviously, not the same
methology as Yocto. With some success with the current methods, it's
I thought the idea was to build a recipe for your device that could create
the software complete with all the pieces. Certainly, having a list of
packages that you need to install via zypper is fine, but I thought that
not the concept behind Yocto???
Sorry for the dumb questions.
Jim A
On Mon,
Hi James,
On Mon, Nov 7, 2011 at 1:59 PM, James Abernathy jfaberna...@gmail.comwrote:
I approach embedded Linux from a path of taking a Distro like Ubuntu or
Fedora and chopping it down to a working set of code that forms the final
solution. Obviously, not the same methology as Yocto. With
On 2011-11-07 15:15, James Abernathy wrote:
I thought the idea was to build a recipe for your device that could create the
software complete with all the pieces. Certainly, having a list of packages
that you need to install
via zypper is fine, but I thought that not the concept behind Yocto???
On Nov 7, 2011, at 7:12 PM, Gary Thomas wrote:
On 2011-11-07 15:15, James Abernathy wrote:
I thought the idea was to build a recipe for your device that could create
the software complete with all the pieces. Certainly, having a list of
packages that you need to install
via zypper is
when using the yocto ADT in eclipse, I want to specify the toolchain
location by path variables, but only got error!
It looks like other preference can support the path variable.
any ideas?
I want to use build system direved toolchain, for which the
toolchain/sysroots/kernel are all located in
23 matches
Mail list logo
