Trying to build poky on master and I recieve the following error with
sgml-common-native:
ERROR: Function failed: sgml_common_sstate_postinst (see
/home/jack/Projects/poky-denzil.git/r0005/tmp/work/x86_64-linux/sgml-common-native-0.6.3-r0/temp/log.do_populate_sysroot.4701
for further
On Thu, 2012-06-14 at 15:26 +0200, Björn Stenberg wrote:
Many source packages include their own package test suites. We are
looking at running these tests on target in a structured way, and I
would like a discussion about how to best fit this into the Yocto
framework.
The actions that need
Hi All,
I'm watching console output of 'bitbake minimal-core-image'
It starts with getting native devtools like,
NOTE: Running task 1 of 63 (ID: 11,
/home/bsjang/poky/meta/recipes-devtools/quilt/quilt-native_0.60.bb,
do_fetch)
NOTE: Running task 2 of 63 (ID: 53,
On Fri, 2012-06-15 at 14:10 -0700, Tim Bird wrote:
One of our early efforts, getting busybox
to not fork commands in init scripts that it had as
builtins, proved to be a significant feature that is still
valuable today to improve boot time.
I'd add that one thing we did with Poky's init
On Mon, 2012-06-18 at 20:48 +0900, Bongseo Jang wrote:
Hi All,
I'm watching console output of 'bitbake minimal-core-image'
It starts with getting native devtools like,
NOTE: Running task 1 of 63 (ID:
11, /home/bsjang/poky/meta/recipes-devtools/quilt/quilt-native_0.60.bb,
do_fetch)
On 06/18/2012 01:43 PM, Richard Purdie wrote:
On Thu, 2012-06-14 at 15:26 +0200, Björn Stenberg wrote:
Many source packages include their own package test suites. We are
looking at running these tests on target in a structured way, and I
would like a discussion about how to best fit this into
Fredrik Hugosson wrote:
I think you both might be missing some cases here. The problem is
that 'make check' does not have a standardized meaning.
Even if there was a standardized meaning to make check, there are lots of
packages that use completely differents systems for their building and
Richard Purdie wrote:
c) (-ptest) Install all test files to /opt/ptest/${PN}-${PV} (for
example). Make a package ptest-runner that has a
script /opt/ptest/run-all-tests to iterate over all installed tests
and run them. This is our suggestion.
Can we suitably extract the tests out of the
Add a missing } in the FILESEXTRAPATHS assignment.
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
common/recipes-kernel/linux-firmware/linux-firmware_git.bbappend |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
I'm trying to build using the code sourcery external compiler and I noticed
that it's pulling in qemu. This brings up 2 questions-
1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
prerequisite for building with CS.
2. How can I easily generate a dependency tree so I can
given the number of mailing lists related to yocto and its
components, is there somewhere a decent summary of what topics are
relevant for what lists?
at last count, i see at least the following lists that relate in one
form or another to the final yocto project:
* oe-core
* oe-devel
*
On Mon, Jun 18, 2012 at 11:58 AM, Jim Rucker linux.mrjim...@gmail.com wrote:
I'm trying to build using the code sourcery external compiler and I noticed
that it's pulling in qemu. This brings up 2 questions-
1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
Fix job control in the root shell on poky-tiny images by adding SETSID and
CTTYHACK support to busybox and providing a simple tiny-init startup script.
The following changes since commit e0a70547069fe7e8a2d6bdaffc985fb172d46c31:
perl: Allow perl to cross build and native build in a directory
When building very small systems, it can be useful to spawn a shell from
a simple init script, rather than a full System V Init process. This
requires the shell be the session leader and be able to open the
controlling terminal if it is to have job control.
Create a busybox bbappend in meta-yocto
Currently poky-tiny images will boot and run /bin/sh, which results in
error messages to the console about being unable to open the tty and job
control being disabled.
The shell must be session leader to open the tty, and the tty must not
be /dev/console (it should be a vt or a physical tty like
diving back into the docs, i see that the current development manual
claims, The Yocto Project Development Manual, however, does provide
detailed examples on how to create a Board Support Package (BSP)...
but why? there *is* a separate BSP guide. should the reader not be
referred to the
From: Tom Zanussi tom.zanu...@intel.com
This updates some Yocto BSP templates to fix some recent metadata changes
that caused the problems seen in YOCTO #2559.
Please pull into poky/master.
The following changes since commit 4ff6160d909e2a39e357c8a51f37d803dab64d5d:
Richard Purdie (1):
From: Tom Zanussi tom.zanu...@intel.com
Some changes in the ordering assumptions of the qemu include rendered
X inoperative, fix those in the qemu machine template.
Fixes [YOCTO #2559]
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../arch/qemu/conf/machine/{{=machine}}.conf |
From: Tom Zanussi tom.zanu...@intel.com
The non-x86 qemu machines now require an xorg.conf, change the
templates accordingly.
Fixes [YOCTO #2559]
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
.../xserver-xf86-config/{{=machine}}/xorg.conf |8
...x86_64\: }}
Hey Robert,
The BSP Guide currently is focused on the BSP layout, layers, tools, and
licensing. The Development Manual covers more overall development scenarios,
of which the BSP is one of them. That is the rationale at the moment.
Scott
-Original Message-
From:
On Mon, 18 Jun 2012, Rifenbark, Scott M wrote:
Hey Robert,
The BSP Guide currently is focused on the BSP layout, layers, tools,
and licensing. The Development Manual covers more overall
development scenarios, of which the BSP is one of them. That is the
rationale at the moment.
ok, i'm
I needed to do some network performance testing on a Crownbay board and
needed iperf in that environment. Since I had the core-image-sato-sdk
image created, I just booted that and took the tarball from Sourceforge
and built it per the readme file instructions:
./configure
make
make install
diff --git a/meta-yocto/recipes-core/tiny-init/files/init
b/meta-yocto/recipes-core/tiny-init/files/init
new file mode 100644
index 000..bf2817d
--- /dev/null
+++ b/meta-yocto/recipes-core/tiny-init/files/init
@@ -0,0 +1,21 @@
+#!/bin/sh
+
+# Mount the Linux kernel virtual
On 06/18/2012 02:06 PM, Khem Raj wrote:
diff --git a/meta-yocto/recipes-core/tiny-init/files/init
b/meta-yocto/recipes-core/tiny-init/files/init
new file mode 100644
index 000..bf2817d
--- /dev/null
+++ b/meta-yocto/recipes-core/tiny-init/files/init
@@ -0,0 +1,21 @@
+#!/bin/sh
+
If I build the RPi kernel (SRCREV 3fc65f9f291fb19cad434968a4a0f66ab749e637)
then the board boots as expected.
However, if a modify the .config (either manually after -c configure, or by -c
menuconfig) so that CONFIG_SND, CONFIG_SND_TIMER, CONFIG_SND_PCM and
CONFIG_BCM2835 are set to 'y' (i.e.
On Mon, Jun 18, 2012 at 02:11:58PM -0700, Darren Hart wrote:
On 06/18/2012 02:06 PM, Khem Raj wrote:
diff --git a/meta-yocto/recipes-core/tiny-init/files/init
b/meta-yocto/recipes-core/tiny-init/files/init
new file mode 100644
index 000..bf2817d
--- /dev/null
+++
jfabernathy jfaberna...@gmail.com writes:
I needed to do some network performance testing on a Crownbay board and
needed iperf in that environment. Since I had the core-image-sato-sdk
image created, I just booted that and took the tarball from Sourceforge
and built it per the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/18/2012 02:18 PM, Martin Jansa wrote:
On Mon, Jun 18, 2012 at 02:11:58PM -0700, Darren Hart wrote:
On 06/18/2012 02:06 PM, Khem Raj wrote:
diff --git a/meta-yocto/recipes-core/tiny-init/files/init
On Mon, Jun 18, 2012 at 2:18 PM, Martin Jansa martin.ja...@gmail.com wrote:
what if someone is using
tiny-init in image with coreutils/util-linux/whatever is needed to
execute /init without busybox?
it wont work. Thats why I asked for rdepend
___
Hi,
I see a build fail for grub-efi-native_1.99 recipe in master branch for
Cedartrail BSP.
NOTE: package grub-efi-i586-native-1.99-r9: task do_compile: Started
ERROR: Function failed: do_compile (see
On 06/18/2012 03:10 PM, Bodke, Kishore K wrote:
Hi,
I see a build fail for grub-efi-native_1.99 recipe in master branch for
Cedartrail BSP.
Appears to be the same as:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2527
Thanks,
Darren
NOTE: package grub-efi-i586-native-1.99-r9:
On 18 June 2012 13:06, Robert P. J. Day rpj...@crashcourse.ca wrote:
given the number of mailing lists related to yocto and its
components, is there somewhere a decent summary of what topics are
relevant for what lists?
at last count, i see at least the following lists that relate in one
On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy jfaberna...@gmail.com wrote:
On 06/18/2012 05:21 PM, Marc Ferland wrote:
jfabernathyjfabernathy@gmail.**com jfaberna...@gmail.com writes:
I needed to do some network performance testing on a Crownbay board and
needed iperf in that
On Monday, June 18, 2012, James Abernathy jfaberna...@gmail.com wrote:
On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy jfaberna...@gmail.com
wrote:
On 06/18/2012 05:21 PM, Marc Ferland wrote:
jfabernathyjfaberna...@gmail.com writes:
I needed to do some network performance testing on a
34 matches
Mail list logo
