[yocto] Build fails moving from 4.0.1 to 5.0.1
I've got a configuration that builds ok under 4.0.1, but when I build under 5.0.1 I get the following right at the end: Installing task-poky-boot (1.0-r7) to root... Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk. Installing task-sjs (1.0-r0) to root... Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk. Unknown package 'run-postinsts'. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-poky-boot: * tinylogin * busybox * modutils-initscripts * initscripts * console-tools * initscripts * udev * sysvinit * netbase * base- passwd * * opkg_install_cmd: Cannot install package task-poky-boot. * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-sjs: * yocto-wallboard * psplash * syslinux * * opkg_install_cmd: Cannot install package task-sjs. * opkg_install_cmd: Cannot install package run-postinsts. ERROR: Function 'do_rootfs' failed (see ... If I look in tmp/work, it looks as if the missing dependencies have all been built and packaged within their work areas. I tried cleaning and rebuilding 'task-sjs', but that made no difference to the errors reported against it. Where should I start looking to work out what's going wrong here? Is it as simple as needing to add something like RDEPENDS? Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] script/runqemu: change boot command line for qemuppc
Because qemuppc has no graphic emulation, remove console=tty0 and make it run into 3 run level. This can reduce boot time for qemuppc booting. Signed-off-by: Liming Wang --- scripts/runqemu-internal |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal index c15632d..883fa5b 100755 --- a/scripts/runqemu-internal +++ b/scripts/runqemu-internal @@ -384,7 +384,7 @@ if [ "$MACHINE" = "qemuppc" ]; then BIOS=powerpc_rom.bin QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -nographic" if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then -KERNCMDLINE="root=/dev/hda rw console=ttyS0 console=tty0 $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" +KERNCMDLINE="root=/dev/hda rw console=ttyS0 3 $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE -bios $BIOS -hda $ROOTFS -no-reboot $QEMU_UI_OPTIONS" fi if [ "$FSTYPE" = "nfs" ]; then @@ -393,7 +393,7 @@ if [ "$MACHINE" = "qemuppc" ]; then cleanup return fi -KERNCMDLINE="root=/dev/nfs console=ttyS0 console=tty0 nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" +KERNCMDLINE="root=/dev/nfs console=ttyS0 3 nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE -bios $BIOS -no-reboot $QEMU_UI_OPTIONS" fi fi -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] meta: add APM Emulation option to beagleboard
On 08/19/2011 02:43 AM, walimis wrote: > From: Liming Wang > > apmd daemon needs this option to work, so add this to beagleboard > kernel config file. > > Signed-off-by: Liming Wang I'd like to move beyond this in the future, but for the 1.1 release I think this is the right call: Acked-by: Darren Hart > --- > .../kernel-cache/bsp/beagleboard/beagleboard.cfg |5 + > 1 files changed, 5 insertions(+), 0 deletions(-) > > diff --git a/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg > b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg > index 00485d2..56fce58 100644 > --- a/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg > +++ b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg > @@ -328,3 +328,8 @@ CONFIG_VIDEO_OMAP3_ISP=y > # CONFIG_VIDEO_OMAP34XX_ISP_PREVIEWER is not set > CONFIG_VIDEO_OMAP34XX_ISP_RESIZER=y > # CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set > + > +# > +# Advanced Power Management Emulation support > +# > +CONFIG_APM_EMULATION=y -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] script/runqemu: change boot command line for qemuppc
On 08/19/2011 03:06 AM, Liming Wang wrote: > Because qemuppc has no graphic emulation, remove console=tty0 > and make it run into 3 run level. This can reduce boot time > for qemuppc booting. > > Signed-off-by: Liming Wang Acked-by: Darren Hart > --- > scripts/runqemu-internal |4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal > index c15632d..883fa5b 100755 > --- a/scripts/runqemu-internal > +++ b/scripts/runqemu-internal > @@ -384,7 +384,7 @@ if [ "$MACHINE" = "qemuppc" ]; then > BIOS=powerpc_rom.bin > QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -nographic" > if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then > -KERNCMDLINE="root=/dev/hda rw console=ttyS0 console=tty0 > $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" > +KERNCMDLINE="root=/dev/hda rw console=ttyS0 3 $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE > -bios $BIOS -hda $ROOTFS -no-reboot $QEMU_UI_OPTIONS" > fi > if [ "$FSTYPE" = "nfs" ]; then > @@ -393,7 +393,7 @@ if [ "$MACHINE" = "qemuppc" ]; then > cleanup > return > fi > -KERNCMDLINE="root=/dev/nfs console=ttyS0 console=tty0 > nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > +KERNCMDLINE="root=/dev/nfs console=ttyS0 3 > nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE > -bios $BIOS -no-reboot $QEMU_UI_OPTIONS" > fi > fi -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 06/12] meta-crownbay: update README
On Thu, 2011-08-18 at 13:53 -0500, Tom Zanussi wrote:
> On Thu, 2011-08-18 at 11:12 -0700, Saul Wold wrote:
> > On 08/17/2011 09:51 AM, tom.zanu...@intel.com wrote:
> > > From: Tom Zanussi
> > >
> > > With the new emgd-driver-bin recipe, the extensive instructions on how
> > > to manually download and set up EMGD for the build are no longer
> > > necessary. Those instructions have been replaced with the simpler set
> > > of instructions now needed to build crownbay with EMGD.
> > >
> > > Changes to reflect the new image names and a couple other minor
> > > cleanups are also included.
> > >
> > > Signed-off-by: Tom Zanussi
> > > ---
> > > meta-crownbay/README | 207
> > > ++
> > > 1 files changed, 42 insertions(+), 165 deletions(-)
> > >
> > > diff --git a/meta-crownbay/README b/meta-crownbay/README
> > > index 89056ed..c82f2c4 100644
> > > --- a/meta-crownbay/README
> > > +++ b/meta-crownbay/README
> > > @@ -6,7 +6,7 @@ The Crown Bay platform consists of the Intel Atom Z6xx
> > > processor,
> > > plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> > >
> > > It also supports the E6xx embedded on-chip graphics via the Intel
> > > -Embedded Media and Graphics Driver (EMGD) 1.6 Gold Driver.
> > > +Embedded Media and Graphics Driver (EMGD) 1.8 Driver.
> > >
> > > Table of Contents
> > > =
> > > @@ -33,14 +33,20 @@ bblayers.conf e.g.:
> > > The meta-crownbay layer contains support for two different machine
> > > configurations. These configurations are identical except for the fact
> > > that the one prefixed with 'crownbay' makes use of the
> > > -Intel-proprietary EMGD 1.6 graphics driver, while the one prefixed
> > > +Intel-proprietary EMGD 1.8 graphics driver, while the one prefixed
> > > with 'crownbay-noemgd' does not.
> > >
> > > -If you want to enable the layer that supports EMGD graphics add
> > > +If you want to enable the layer that supports EMGD graphics add the
> > > following to the local.conf file:
> > >
> > > MACHINE ?= "crownbay"
> > >
> > > +You also need to add the line:
> > > +
> > > + COMMERCIAL_LICENSE = ""
> > > +
> > Tom,
> >
> > I thought we talked about using the oe_filter mechanism here instead of
> > a flat override, since this will bring in other COMMERCIAL_LICENSED content.
> >
>
> Right, but it doesn't work and isn't exactly user-friendly:
>
> COMMERCIAL_LICENSE := "${@oe_filter_out('emgd-driver-bin',
> '${COMMERCIAL_LICENSE}', d)}"
>
> gives:
>
> trz@elmorro:/usr/local/src/yocto/newkern/build$ bitbake core-image-sato
> ERROR: Unable to parse conf/bitbake.conf: Failure expanding variable
> COMMERCIAL_LICENSE[:=], expression was
> ${@oe_filter_out('emgd-driver-bin', ' emgd-driver-bin', d)} which
> triggered exception NameError: name 'oe_filter_out' is not defined
>
> I both sent you this result and pinged you on IRC about this before I
> posted the new version that also includes the patch "meta-intel:
> crownbay/fri2 README update for COMMERCIAL_LICENSE" containing another
> method if the other is too broad to specifically address your concern:
>
> +Alternatively, if clearing COMMERCIAL_LICENSE is not precise enough
> +for your needs, you can also simply comment out the following line in
> +meta-crownbay/conf/layer.conf to achieve the same result:
> +
> + COMMERCIAL_LICENSE += "emgd-driver-bin"
>
> Also, the COMMERCIAL_LICENSE = "" flat override method presents the same
> problem for anyone wanting to bring in only one of the packages in the
> existing COMMERCIAL_LICENSE list in default-distrovars. The flat
> override is always answer on the list given whenever people try to use
> those recipes (none of this is documented anywhere that I could find
> BTW). So how is this different?
>
> If you can give me a better method that works, I'll be glad to update it
> with that.
>
Saul, can you either Ack or NAK this patchset - it's been out there for
a week now and I'd like to be able to pull it in...
Thanks,
Tom
> Tom
>
> > Sau!
> >
> > > +to the local.conf file.
> > > +
> > > If you want to enable the layer that does not support EMGD graphics
> > > add the following to the local.conf file:
> > >
> > > @@ -48,8 +54,8 @@ add the following to the local.conf file:
> > >
> > > You should then be able to build a crownbay image as such:
> > >
> > > - $ source poky-init-build-env
> > > - $ bitbake poky-image-sato-live
> > > + $ source oe-init-build-env
> > > + $ bitbake core-image-sato
> > >
> > > At the end of a successful build, you should have a live image that
> > > you can boot from a USB flash drive (see instructions on how to do
> > > @@ -59,10 +65,11 @@ As an alternative to downloading the BSP tarball, you
> > > can also work
> > > directly from the meta-intel git repository. For each BSP in the
> > > 'meta-intel' repository, there are multiple branches, one
> > > corresponding to each major release starting with 'laverne' (0.90), i
[yocto] [PATCH] meta: add APM Emulation option to beagleboard
From: Liming Wang apmd daemon needs this option to work, so add this to beagleboard kernel config file. Signed-off-by: Liming Wang --- .../kernel-cache/bsp/beagleboard/beagleboard.cfg |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg index 00485d2..56fce58 100644 --- a/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg +++ b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg @@ -328,3 +328,8 @@ CONFIG_VIDEO_OMAP3_ISP=y # CONFIG_VIDEO_OMAP34XX_ISP_PREVIEWER is not set CONFIG_VIDEO_OMAP34XX_ISP_RESIZER=y # CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set + +# +# Advanced Power Management Emulation support +# +CONFIG_APM_EMULATION=y -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build fails moving from 4.0.1 to 5.0.1
On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote: > I've got a configuration that builds ok under 4.0.1, but when I build > under 5.0.1 I get the following right at the end: > > Installing task-poky-boot (1.0-r7) to root... > Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ > Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk. > Installing task-sjs (1.0-r0) to root... > Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ > Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk. > Unknown package 'run-postinsts'. > Collected errors: > * satisfy_dependencies_for: Cannot satisfy the following > dependencies for task-poky-boot: > * tinylogin * busybox * modutils-initscripts * initscripts * > > console-tools * initscripts * udev * sysvinit * netbase * > base- > passwd * > * opkg_install_cmd: Cannot install package task-poky-boot. > * satisfy_dependencies_for: Cannot satisfy the following > dependencies for task-sjs: > * yocto-wallboard * psplash * syslinux * > * opkg_install_cmd: Cannot install package task-sjs. > * opkg_install_cmd: Cannot install package run-postinsts. > ERROR: Function 'do_rootfs' failed (see ... > > If I look in tmp/work, it looks as if the missing dependencies have > all been built and packaged within their work areas. > > I tried cleaning and rebuilding 'task-sjs', but that made no > difference to the errors reported against it. > > Where should I start looking to work out what's going wrong here? Is > it as simple as needing to add something like RDEPENDS? This sounds like the machine specific packages are failing to be found so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS isn't listing everything it needs to (such as the machine name) or the package system isn't finding a group of packages for some other reason. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] script/runqemu: change boot command line for qemuppc
On Fri, 2011-08-19 at 18:06 +0800, Liming Wang wrote: > Because qemuppc has no graphic emulation, remove console=tty0 > and make it run into 3 run level. This can reduce boot time > for qemuppc booting. > > Signed-off-by: Liming Wang > --- > scripts/runqemu-internal |4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal > index c15632d..883fa5b 100755 > --- a/scripts/runqemu-internal > +++ b/scripts/runqemu-internal > @@ -384,7 +384,7 @@ if [ "$MACHINE" = "qemuppc" ]; then > BIOS=powerpc_rom.bin > QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -nographic" > if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then > -KERNCMDLINE="root=/dev/hda rw console=ttyS0 console=tty0 > $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY" > +KERNCMDLINE="root=/dev/hda rw console=ttyS0 3 $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE > -bios $BIOS -hda $ROOTFS -no-reboot $QEMU_UI_OPTIONS" > fi > if [ "$FSTYPE" = "nfs" ]; then > @@ -393,7 +393,7 @@ if [ "$MACHINE" = "qemuppc" ]; then > cleanup > return > fi > -KERNCMDLINE="root=/dev/nfs console=ttyS0 console=tty0 > nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > +KERNCMDLINE="root=/dev/nfs console=ttyS0 3 > nfsroot=$NFS_SERVER:$NFS_DIR,$UNFS_OPTS rw $KERNEL_NETWORK_CMD > mem=$QEMU_MEMORY" > QEMUOPTIONS="$QEMU_NETWORK_CMD -cpu $CPU_SUBTYPE -M $MACHINE_SUBTYPE > -bios $BIOS -no-reboot $QEMU_UI_OPTIONS" > fi > fi Can we not fix the X scripts so that if an fbdev X server is in use and the framebuffer device node does not exist, it just exits cleanly with a suitable message and doesn't timeout on boot? Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build fails moving from 4.0.1 to 5.0.1
On 19 Aug 2011, at 17:16, Richard Purdie wrote: On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote: I've got a configuration that builds ok under 4.0.1, but when I build under 5.0.1 I get the following right at the end: Installing task-poky-boot (1.0-r7) to root... Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk. Installing task-sjs (1.0-r0) to root... Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk. Unknown package 'run-postinsts'. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-poky-boot: * tinylogin * busybox * modutils-initscripts * initscripts * console-tools * initscripts * udev * sysvinit * netbase * base- passwd * * opkg_install_cmd: Cannot install package task-poky-boot. * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-sjs: * yocto-wallboard * psplash * syslinux * * opkg_install_cmd: Cannot install package task-sjs. * opkg_install_cmd: Cannot install package run-postinsts. ERROR: Function 'do_rootfs' failed (see ... If I look in tmp/work, it looks as if the missing dependencies have all been built and packaged within their work areas. I tried cleaning and rebuilding 'task-sjs', but that made no difference to the errors reported against it. Where should I start looking to work out what's going wrong here? Is it as simple as needing to add something like RDEPENDS? This sounds like the machine specific packages are failing to be found so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS isn't listing everything it needs to (such as the machine name) or the package system isn't finding a group of packages for some other reason. Thanks, but that's way over my head at the moment ;-) I've searched through the meta data for PACKAGE_ARCHS, but that's not thrown anything up to make me think there was anything I should look at. I'm using my own machine recipe. Is this were I should be looking? Chris ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build fails moving from 4.0.1 to 5.0.1
On Fri, 2011-08-19 at 20:43 +0100, Chris Tapp wrote: > On 19 Aug 2011, at 17:16, Richard Purdie wrote: > > > On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote: > >> I've got a configuration that builds ok under 4.0.1, but when I build > >> under 5.0.1 I get the following right at the end: > >> > >> Installing task-poky-boot (1.0-r7) to root... > >> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ > >> Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk. > >> Installing task-sjs (1.0-r0) to root... > >> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/ > >> Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk. > >> Unknown package 'run-postinsts'. > >> Collected errors: > >> * satisfy_dependencies_for: Cannot satisfy the following > >> dependencies for task-poky-boot: > >> * tinylogin * busybox * modutils-initscripts * > >> initscripts * > >> console-tools *initscripts * udev * sysvinit * netbase * > >> base- > >> passwd * > >> * opkg_install_cmd: Cannot install package task-poky-boot. > >> * satisfy_dependencies_for: Cannot satisfy the following > >> dependencies for task-sjs: > >> * yocto-wallboard * psplash * syslinux * > >> * opkg_install_cmd: Cannot install package task-sjs. > >> * opkg_install_cmd: Cannot install package run-postinsts. > >> ERROR: Function 'do_rootfs' failed (see ... > >> > >> If I look in tmp/work, it looks as if the missing dependencies have > >> all been built and packaged within their work areas. > >> > >> I tried cleaning and rebuilding 'task-sjs', but that made no > >> difference to the errors reported against it. > >> > >> Where should I start looking to work out what's going wrong here? Is > >> it as simple as needing to add something like RDEPENDS? > > > > This sounds like the machine specific packages are failing to be found > > so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS > > isn't listing everything it needs to (such as the machine name) or the > > package system isn't finding a group of packages for some other > > reason. > > Thanks, but that's way over my head at the moment ;-) > > I've searched through the meta data for PACKAGE_ARCHS, but that's not > thrown anything up to make me think there was anything I should look at. > > I'm using my own machine recipe. Is this were I should be looking? Yes, I suspect something about your machine config is resulting in this but its hard to me to say what. You can do things like "bitbake -e | grep ^PACKAGE_ARCHS" to see the contents of variables. I'm curious if your machine name is listed in that list. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build fails moving from 4.0.1 to 5.0.1
On 19 Aug 2011, at 21:49, Richard Purdie wrote:
On Fri, 2011-08-19 at 20:43 +0100, Chris Tapp wrote:
On 19 Aug 2011, at 17:16, Richard Purdie wrote:
On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote:
I've got a configuration that builds ok under 4.0.1, but when I
build
under 5.0.1 I get the following right at the end:
Installing task-poky-boot (1.0-r7) to root...
Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk.
Installing task-sjs (1.0-r0) to root...
Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk.
Unknown package 'run-postinsts'.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following
dependencies for task-poky-boot:
* tinylogin * busybox * modutils-initscripts * initscripts *
console-tools * initscripts * udev * sysvinit * netbase *
base-
passwd *
* opkg_install_cmd: Cannot install package task-poky-boot.
* satisfy_dependencies_for: Cannot satisfy the following
dependencies for task-sjs:
* yocto-wallboard * psplash * syslinux *
* opkg_install_cmd: Cannot install package task-sjs.
* opkg_install_cmd: Cannot install package run-postinsts.
ERROR: Function 'do_rootfs' failed (see ...
If I look in tmp/work, it looks as if the missing dependencies have
all been built and packaged within their work areas.
I tried cleaning and rebuilding 'task-sjs', but that made no
difference to the errors reported against it.
Where should I start looking to work out what's going wrong here?
Is
it as simple as needing to add something like RDEPENDS?
This sounds like the machine specific packages are failing to be
found
so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS
isn't listing everything it needs to (such as the machine name) or
the
package system isn't finding a group of packages for some other
reason.
Thanks, but that's way over my head at the moment ;-)
I've searched through the meta data for PACKAGE_ARCHS, but that's not
thrown anything up to make me think there was anything I should
look at.
I'm using my own machine recipe. Is this were I should be looking?
Yes, I suspect something about your machine config is resulting in
this
but its hard to me to say what.
You can do things like "bitbake -e | grep ^PACKAGE_ARCHS" to see the
contents of variables. I'm curious if your machine name is listed in
that list.
chris@ubuntu:~/yocto/ebox3300-build$ bitbake -e |grep "PACKAGE_ARCHS"
# PACKAGE_ARCHS=all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}
PACKAGE_ARCHS="all any noarch x86 Vortex86DX"
ipkg_archs = bb.data.getVar('PACKAGE_ARCHS',d)
bb.error("PACKAGE_ARCHS missing")
My machine is "Vortex86DX"
Chris Tapp
opensou...@keylevel.com
www.keylevel.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build fails moving from 4.0.1 to 5.0.1
On Fri, 2011-08-19 at 21:58 +0100, Chris Tapp wrote:
> On 19 Aug 2011, at 21:49, Richard Purdie wrote:
>
> > On Fri, 2011-08-19 at 20:43 +0100, Chris Tapp wrote:
> >> On 19 Aug 2011, at 17:16, Richard Purdie wrote:
> >>
> >>> On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote:
> I've got a configuration that builds ok under 4.0.1, but when I
> build
> under 5.0.1 I get the following right at the end:
>
> Installing task-poky-boot (1.0-r7) to root...
> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk.
> Installing task-sjs (1.0-r0) to root...
> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk.
> Unknown package 'run-postinsts'.
> Collected errors:
> * satisfy_dependencies_for: Cannot satisfy the following
> dependencies for task-poky-boot:
> *tinylogin * busybox * modutils-initscripts *
> initscripts *
> console-tools * initscripts * udev * sysvinit * netbase *
>
> base-
> passwd *
> * opkg_install_cmd: Cannot install package task-poky-boot.
> * satisfy_dependencies_for: Cannot satisfy the following
> dependencies for task-sjs:
> *yocto-wallboard * psplash * syslinux *
> * opkg_install_cmd: Cannot install package task-sjs.
> * opkg_install_cmd: Cannot install package run-postinsts.
> ERROR: Function 'do_rootfs' failed (see ...
>
> If I look in tmp/work, it looks as if the missing dependencies have
> all been built and packaged within their work areas.
>
> I tried cleaning and rebuilding 'task-sjs', but that made no
> difference to the errors reported against it.
>
> Where should I start looking to work out what's going wrong here?
> Is
> it as simple as needing to add something like RDEPENDS?
> >>>
> >>> This sounds like the machine specific packages are failing to be
> >>> found
> >>> so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS
> >>> isn't listing everything it needs to (such as the machine name) or
> >>> the
> >>> package system isn't finding a group of packages for some other
> >>> reason.
> >>
> >> Thanks, but that's way over my head at the moment ;-)
> >>
> >> I've searched through the meta data for PACKAGE_ARCHS, but that's not
> >> thrown anything up to make me think there was anything I should
> >> look at.
> >>
> >> I'm using my own machine recipe. Is this were I should be looking?
> >
> > Yes, I suspect something about your machine config is resulting in
> > this
> > but its hard to me to say what.
> >
> > You can do things like "bitbake -e | grep ^PACKAGE_ARCHS" to see the
> > contents of variables. I'm curious if your machine name is listed in
> > that list.
>
> chris@ubuntu:~/yocto/ebox3300-build$ bitbake -e |grep "PACKAGE_ARCHS"
>
> # PACKAGE_ARCHS=all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}
> PACKAGE_ARCHS="all any noarch x86 Vortex86DX"
> ipkg_archs = bb.data.getVar('PACKAGE_ARCHS',d)
> bb.error("PACKAGE_ARCHS missing")
>
> My machine is "Vortex86DX"
What does "ls /home/chris/yocto/ebox3300-build/tmp/deploy/ipk" say?
Cheers,
Richard
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Technical Team Meeting - (Tuesday, August 23, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada))
Agenda * Opens collection - 5 min (Song) * Yocto 1.1 M4 status review and issues - 20 min (team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria#Milestone_ - Build and QA status (Beth/Song) - Release criteria review (Song) . Bug fixing . High bugs . Build performance * Opens * Action item review Action Item List: * Song to update wiki page and the Google calendar for w4 schedules. * Song to schedule the go/no-go meeting for M3. * Richard to follow up with Mark on bug 1325 to decide if we need this for M3 once we have the resolutions. * Song to follow up with ScottR offline on doc issues: auto-generation, revisions, central location for docs changes, etc. Conference details Conference name: Yocto Technical Team Conference date/start time: Tue Jun 28, 2011 at 10:00 AM Central Daylight Time Participants: 30 Duration: 60 minutes Participant passcode: 49611427 Dial-in number: 1.972.995. US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a chairperson: 1.972.995.x67184230# BlackBerry users, click this link to join your conference as a participant: 1.972.995.x49611427# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): >From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): >From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): >From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): >From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) >From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: >From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: >From IP phone dial 2643799 >From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: >From Baguio City use 4471177 >From Metro Manila area use 8702477 Singapore: >From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: >From IP phone dial 5606998 >From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: >From IP phone dial 1363 >From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01604 663003 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 28, 2011 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends: End on Fri Jun 22, 2012, 10:40 AM CDT ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] beagleboard: enable hard floating point abi
There have been requests to enable the hard floating point abi for the Yocto Project Beagleboard BSP. With the recent cortexa8 tune file changes I submitted to oe-core, subject "tune: update arm7a and cortexa8 tune files", it is now possible for the machine config to change DEFAULTTUNE to take advantage of the newly added "hf" tune variants. Some binary libraries are incompatible with hardfp, as is 3D support on the Beagleboard. We don't ship either, so I feel it makes sense to take advantage of as much of the core CPU features as possible. This addresses [YOCTO 1203] http://bugzilla.yoctoproject.org/show_bug.cgi?id=1204 I don't feel very strongly about this however. So if someone would like to argue for hardfp not being the default, please do so and I can easily comment out the DEFAULTTUNE change and add a comment in the machine config describing how to enable hardfp. The following changes since commit 53bdf3fd520b75730cc802f52121dd394894e130: tune: Add hard floating point variants of cortexa8 tunes (2011-08-19 15:02:10 -0700) are available in the git repository at: git://git.pokylinux.org/poky-contrib dvhart/beagleboard-hardfp http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/beagleboard-hardfp Darren Hart (1): beagleboard: enable hard floating point abi meta-yocto/conf/machine/beagleboard.conf |5 + 1 files changed, 5 insertions(+), 0 deletions(-) -- 1.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] beagleboard: enable hard floating point abi
Fixes [YOCTO #1203] Using the hard floating point abi is incompatible with some binary libaries and 3D support for the Beagleboard. As we do not provide these in poky and meta-yocto, we can take advantage of the hard floating point abi. This can be easily disabled by anyone building on top of meta-yocto if they need the soft abi by overriding DEFAULT_TUNE. Signed-off-by: Darren Hart CC: Jason Kridner CC: Koen Kooi --- meta-yocto/conf/machine/beagleboard.conf |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/meta-yocto/conf/machine/beagleboard.conf b/meta-yocto/conf/machine/beagleboard.conf index 0b3cebc..8f11732 100644 --- a/meta-yocto/conf/machine/beagleboard.conf +++ b/meta-yocto/conf/machine/beagleboard.conf @@ -18,6 +18,11 @@ MACHINE_EXTRA_RRECOMMENDS += "beagleboard-audio" # Allow for MMC booting (required by the NAND-less Beagleboard XM) EXTRA_IMAGEDEPENDS += "u-boot x-load" +# Use the hard floating point abi. This breaks some binary libraries and +# 3D. Since poky and meta-yocto do not provide these by default, enable the +# hard floating point abi. Comment out the following or override it to disable +# it. +DEFAULTTUNE ?= "cortexa8hf-neon" include conf/machine/include/tune-cortexa8.inc IMAGE_FSTYPES += "tar.bz2 jffs2" -- 1.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
