I've having some difficulty running hob on Debian wheezy/sid. When
I enter hob from the command line, an X-window opens, but none of
the controls have any text labels. Also, none of the drop-down lists
are populated.
I also see this message on the command prompt:
Gtk-Message: Failed to load
I'm trying to get the core-image-minimal distro to boot in qemu for an
ARM Cortex A9 system. It boots the kernel fine, but croaks when it
tries to run init.
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda): using internal journal
EXT3-fs (sda): recovery complete
EXT3-fs (sda):
do_rootfs is failing when I try to build core-image-minimal on a
debian squeeze box. I am surprised it is trying to do something that
requires root privilege on the host. Any ideas on how to get past
this?
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started
ERROR: Function failed:
Pls disregard. Something got wonked in my build dir. I blew it away
and rebuilt everything. It finished without errors.
On Mon, Jul 23, 2012 at 11:15 AM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
do_rootfs is failing when I try to build core-image-minimal on a
debian squeeze box. I
I'm using a pre-compiled toolchain to build my distro. When I execute
bitbake core-image-minimal, things fail in eglibc.
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
'common']
ERROR: Function failed: do_configure
Is there a way to skip a QA check for more than one package or all packages?
I'd like to avoid having to add a INSANE_SKIP_${PN} += ldflags for
every package that fails due to ERROR: QA Issue: No GNU_HASH in the
elf binary.
There are gobs of python and perl packages failing with this error
when
I'm using an external toolchain for my project. What is the proper
way to include my external toolchain libc files in the sysroot?
Currently I have
TOOLCHAIN_OPTIONS = --sysroot=${STAGING_DIR_HOST}
and
EXTERNAL_TOOLCHAIN_SYSROOT_CMD = ${TARGET_PREFIX}gcc
${TARGET_CC_ARCH} -print-sysroot
Thanks Chris. I was close, just missing the actual copying part from
the do_install() as observed. ;^)
I got quite a bit further. Am running into issues like this now:
ERROR: QA Issue: No GNU_HASH in the elf binary:
On Fri, Jul 13, 2012 at 4:18 PM, Chris Larson clar...@kergoth.com wrote:
On Fri, Jul 13, 2012 at 2:05 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
Thanks Chris. I was close, just missing the actual copying part from
the do_install() as observed. ;^)
I got quite a bit further. Am
I'm trying to use an external pre-built toolchain to build my distro.
I added a TCMODE ?= external-sourcery to my local.conf and modified
the external-sourcery include file as follows:
diff --git a/meta/conf/distro/include/tcmode-external-sourcery.inc
Hi all, Please bear with me as I am a newb to both yocto and building
bsp's. I was able to run bitbake core-image-minimal for x86-64, just fine and
run it in qemu.
Then I got gutsy and tried to build a bsp for ARM. Didn't go so well.
I must be missing something.
dallasc
with the same
errors.
I am using the latest poky tarball - poky-denzil-7.0.tar.bz2
Thanks,
Dallas
On Tue, Jun 19, 2012 at 10:03 AM, Tom Zanussi tom.zanu...@intel.com wrote:
On Tue, 2012-06-19 at 09:37 -0500, Dallas Clement wrote:
Hi all, Please bear with me as I am a newb to both yocto and building
Okay, using the git poky, I was able to build the bsp. It seems that
the tarball version is not able to complete this step:
Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-3.2...
On Tue, Jun 19, 2012 at 10:23 AM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
That's
I have a cross-toolchain supplied by an ARM SoC vendor which I need to
use to build my distro. What is required to use a toolchain like this
instead of one of the yocto cross-toolchain tarballs?
Thanks
___
yocto mailing list
yocto@yoctoproject.org
14 matches
Mail list logo