Re: [yocto] why is "package-management" defined as a PACKAGE_GROUP?

[Paul Eggleton]

Hi Robert,

On Sunday 17 November 2013 11:17:13 Robert P. J. Day wrote:
> On Sun, 17 Nov 2013, Chris Larson wrote:
> 
> ... huge snip that i hope won't be necessary ...
> 
> > This test you did makes no sense. Of course it’s in IMAGE_FEATURES,
> > you put it there. What you didn’t check is whether
> > ${ROOTFS_PKGMANAGE} ended up being installed in the image, which it
> > won’t be.
> 
>   i think i see my basic and fatal misunderstanding, and if you can
> tolerate one more post, i want to make sure i know what i did wrong as
> i want to write this up and i want to be accurate.
> 
>   as i understood it (apparently incorrectly), IMAGE_FEATURES fell
> into two categories:
> 
>   1) actual package groups, as defined in core-image.bbclass, as in:
> 
> PACKAGE_GROUP_x11 = "packagegroup-core-x11"
> PACKAGE_GROUP_x11-base = "packagegroup-core-x11-base"
> PACKAGE_GROUP_x11-sato = "packagegroup-core-x11-sato"

As I keep saying, these aren't package groups despite the name of the 
variable. Please stop calling them that. All they say is that if "x11" is 
present in IMAGE_FEATURES, bring in packagegroup-core-x11. The fact that these 
*do* point to actual package groups as packages is pretty much incidental.

>   2) non-package group values that were processed independently by
> code in image.bbclass, such as "read-only-rootfs" or "debug-tweaks"
> 
>   what i *thought* was that each setting had to be one *or* the other,
> but not both. so when i saw code in image.bbclass that was handling
> the "package-management" IMAGE_FEATURE, i immediately assumed that
> meant it couldn't *also* represent an actual package group. is that
> where i went wrong?
> 
>   so, in this one case for the IMAGE FEATURE "package-management",
> there is an actual package group defined as:
> 
> PACKAGE_GROUP_package-management = "${ROOTFS_PKGMANAGE}"

Not a package group.

> which represents the packages:
> 
> $ bb show -r core-image-base ROOTFS_PKGMANAGE
> Parsing recipes..done.
> # ROOTFS_PKGMANAGE=opkg opkg-collateral ${EXTRAOPKGCONFIG}
> ROOTFS_PKGMANAGE="opkg opkg-collateral poky-feed-config-opkg"
> $
> 
> but that feature *also* pulls in additional processing as it's defined
> in image.bbclass.
> 
>   have i finally got it right?

In that there are several things at work dealing with the single "package-
management" item, yes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] why is "package-management" defined as a PACKAGE_GROUP?

[Robert P. J. Day]

On Mon, 18 Nov 2013, Paul Eggleton wrote:

> Hi Robert,
>
> On Sunday 17 November 2013 11:17:13 Robert P. J. Day wrote:
> > On Sun, 17 Nov 2013, Chris Larson wrote:
> >
> > ... huge snip that i hope won't be necessary ...
> >
> > > This test you did makes no sense. Of course it’s in IMAGE_FEATURES,
> > > you put it there. What you didn’t check is whether
> > > ${ROOTFS_PKGMANAGE} ended up being installed in the image, which it
> > > won’t be.
> >
> >   i think i see my basic and fatal misunderstanding, and if you can
> > tolerate one more post, i want to make sure i know what i did wrong as
> > i want to write this up and i want to be accurate.
> >
> >   as i understood it (apparently incorrectly), IMAGE_FEATURES fell
> > into two categories:
> >
> >   1) actual package groups, as defined in core-image.bbclass, as in:
> >
> > PACKAGE_GROUP_x11 = "packagegroup-core-x11"
> > PACKAGE_GROUP_x11-base = "packagegroup-core-x11-base"
> > PACKAGE_GROUP_x11-sato = "packagegroup-core-x11-sato"
>
> As I keep saying, these aren't package groups despite the name of
> the variable. Please stop calling them that. All they say is that if
> "x11" is present in IMAGE_FEATURES, bring in packagegroup-core-x11.
> The fact that these *do* point to actual package groups as packages
> is pretty much incidental.

  yes, i think i finally figured it out, and it was that variable name
prefix "PACKAGE_GROUP" that kept throwing me. in fact, it might have
been clearer if the terminology used had been:

IMAGE_FEATURE_x11 = "... package list for feature x11 ..."
IMAGE_FEATURE_x11-base = "... package list for feature x11-base ..."

etc, etc. so it's finally sunk in that, no, there's nothing magic
about a "packagegroup", it's just a way of abbreviating a package list
corresponding to a value in IMAGE_FEATURES.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wrong version of busybox after adding new layers.

[Gary Thomas]

On 2013-11-17 17:17, Edward Vidal wrote:

Hello,
MACHINE=zedboard bitbake core-image-sato builds okay.

Build Configuration:
BB_VERSION= "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard"
DISTRO= "poky"
DISTRO_VERSION= "1.4+snapshot-20131117"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = "wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff"
meta-yocto-bsp= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"

NOTE: Running noexec task 5589 of 5595 (ID: 3428, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/gst-meta-base_0.10.bb
 ,
do_build)
NOTE: Running noexec task 5590 of 5595 (ID: 3103, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bb
, do_build)
NOTE: Running noexec task 5591 of 5595 (ID: 2804, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/owl-video-widget/libowl-av_git.bb
 , do_build)
NOTE: Running noexec task 5592 of 5595 (ID: 1583, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/gaku/gaku_git.bb 
, do_build)
NOTE: Running noexec task 5593 of 5595 (ID: 313, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb
, do_build)
NOTE: Running task 5594 of 5595 (ID: 7, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/core-image-sato.bb
 , do_rootfs)
NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Started
NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Succeeded
NOTE: Running noexec task 5595 of 5595 (ID: 12, 
/home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/core-image-sato.bb
 , do_build)
NOTE: Tasks Summary: Attempted 5595 tasks of which 404 didn't need to be rerun 
and all succeeded.

busybox:
   meta 1.21.1
was used.

After adding these 2 lines to bblayers.conf
   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe \
   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia \

bitbake-layers show-layers
layer path  priority
==
meta  /home/vidal/POKY/build111613_zedboard/poky/meta  5
meta-yocto/home/vidal/POKY/build111613_zedboard/poky/meta-yocto  5
meta-oe   
/home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe  6
meta-multimedia   
/home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia  6
meta-xilinx   /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx  8
meta-kc705
/home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-kc705  8
meta-zc702
/home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zc702  8
meta-zedboard 
/home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zedboard  8
meta-yocto-bsp/home/vidal/POKY/build111613_zedboard/poky/meta-yocto-bsp 
 5
[vidal@ws009 build]$ bitbake-layers show-recipes
Parsing recipes..ERROR: No recipes available for:
   
/home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
What is the procedure to us busybox_1.20.2 with the new layers?
Any and all help is appreciated.
Thanks


Refresh your meta-oe layer - this recipe has been updated to match oe-core.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] undocumented MACHINE_FEATURES, and what makes something a MACHINE feature?

[Paul Eggleton]

Hi Robert,

On Saturday 16 November 2013 04:46:13 Robert P. J. Day wrote:
> On Fri, 15 Nov 2013, Burton, Ross wrote:
> > On 15 November 2013 10:49, Robert P. J. Day  wrote:
> > >   as you can see, the only tests for 'wifi' involve either
> > > 
> > > DISTRO_FEATURES or COMBINED_FEATURES, *not* MACHINE_FEATURES
> > > individually. under the circumstances, then, can 'wifi' be
> > > considered a legitimate MACHINE feature if it's never being tested
> > > in that context? (the same can be said for 'bluetooth', by the
> > > way.)
> > 
> > COMBINED_FEATURES is a union of MACHINE_ and DISTRO_FEATURES, so it
> > does make sense for them to be listed as MACHINE_FEATURES as
> > otherwise they can't be combined...  No point building wifi in the
> > distro if the machine doesn't support it, and the machine supporting
> > wifi isn't a reason to enable it in the distro.
> 
>   ok, let me take a shot at clarifying DISTRO_FEATURES versus
> MACHINE_FEATURES since i think there might be some errors in how
> things are being defined, but i'm always delighted to be proven wrong.
> 
>   first, MACHINE_FEATURES. as i read it (and how it's explained in
> section 10.2 of the ref manual), this variable defines simply the
> features for which there is hardware support for any given machine,
> yes? the value of MACHINE_FEATURES says nothing about whether you
> might want to *select* support for that particular feature, it simply
> states the H/W features that are subsequently selectable, is that
> about right?

Yes.

>   because of this, it would *seem* that there's little point in a user
> manipulating the value of this variable outside of the context of an
> actual machine definition file, yes? i mean, if you claim to be
> building for machine "foo", the machine definition file for "foo"
> should set MACHINE_FEATURES properly and that's what you get to work
> with in terms of building your image. so far, so good?

Correct.

>   OTOH, the DISTRO_FEATURES variable allows you to dictate what
> software support you want included in your image, yes? and here's
> where you deal with two cases of selection.
> 
>   in the simpler case, you can select DISTRO features that are
> independent of machine characteristics -- things like ipsec or nfs
> or smbfs. the second case, however, is trickier. the second case deals
> with selectable DISTRO features that require the underlying MACHINE
> feature; otherwise, it wouldn't make any sense(?).

Right.
 
>   example (as before): bluetooth. it makes no sense to select a DISTRO
> feature of bluetooth unless there is underlying hardware for it, and
> that's where this snippet of bitbake.conf comes in:
> 
> COMBINED_FEATURES = "\
> ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "alsa", d)}
> \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "bluetooth",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "ext2",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "vfat",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "irda",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "pcmcia",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "pci",
> d)} \ ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES",
> "usbgadget", d)} \ ${@base_both_contain("DISTRO_FEATURES",
> "MACHINE_FEATURES", "usbhost", d)} \
> ${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "wifi", d)}"
> COMBINED_FEATURES[vardeps] += "DISTRO_FEATURES MACHINE_FEATURES"
> 
> and that's the part i was missing before -- the fact that there is an
> *explicit* list of features for which *both* selections need to be
> true for it to make any sense. so the COMBINED feature of "bluetooth"
> is based on it being both supported in hardware *and* selected as a
> DISTRO feature. (so COMBINED_FEATURES is *not* simply a "union" of
> those other two variables.) and here are some of the apparent
> consequences and oddities i see.
> 
>   first, it would seem that any image definition shouldn't care about
> the setting of MACHINE_FEATURES, should it? as i see it, an image
> should consult only the values of DISTRO_FEATURES and
> COMBINED_FEATURES to see what needs to be included. as ross himself
> wrote:
> 
> "... the machine supporting wifi isn't a reason to enable it in the
> distro."
> 
>   but if i look at, say, oe-core's packagegroup-base.bb recipe file, i
> can see:
> 
> RDEPENDS_packagegroup-base = "\
> packagegroup-distro-base \
> packagegroup-machine-base \
> \
> sysfsutils \
> module-init-tools \
> ${@base_contains('MACHINE_FEATURES', 'apm', 'packagegroup-base-apm',
> '',d)} \ ${@base_contains('MACHINE_FEATURES', 'acpi',
> 'packagegroup-base-acpi', '',d)} \ ${@base_contains('MACHINE_FEATURES',
> 'keyboard', 'packagegroup-base-keyboard', '',d)} \
> ${@base_contains('MACHINE_FEATURES', 'phone', 'packagegroup-base-phone',
> '',d)} \ ... snip ...
> 
> why are those features being included in the imag

Re: [yocto] undocumented MACHINE_FEATURES, and what makes something a MACHINE feature?

[Robert P. J. Day]

   by the way, i am not *trying* to be haplessly confused and
annoying, i am merely succeeding.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] trouble having two toolchain in a single image.

[Anup Kini]

Hi All,

I am trying to install two different toolchain in the same image using
Yocto Poky.
I already built the core-image-minimal which has gcc-4.8 installed in the
image.
When i try to install the second toolchain i get the following message:

The recipe epiphany-gcc is trying to install files into a shared area when
those files already exist. Those files and their manifest location are:

 
/home/akini/poky/build/tmp/sysroots/zc702-zynq7/pkgdata/runtime-reverse/g++-symlinks
   Matched in manifest-zc702-zynq7-gcc.packagedata

 
/home/akini/poky/build/tmp/sysroots/zc702-zynq7/pkgdata/runtime-reverse/cpp-symlinks
   Matched in manifest-zc702-zynq7-gcc.packagedata

 /home/akini/poky/build/tmp/sysroots/zc702-zynq7/pkgdata/runtime-reverse/gcov
   Matched in manifest-zc702-zynq7-gcc.packagedata

 
/home/akini/poky/build/tmp/sysroots/zc702-zynq7/pkgdata/runtime-reverse/gfortran
   Matched in manifest-zc702-zynq7-gcc.packagedata

 /home/akini/poky/build/tmp/sysroots/zc702-zynq7/pkgdata/runtime-reverse/cpp
   Matched in manifest-zc702-zynq7-cpp-common.packagedata



Can i use update-alternative here ?
Kindly let me know how or any example i can look up and realize this.



-- 


*Anup Kini*Systems Engineer
*--*

*Synapticon*  |  Cyber-Physical System Solutions

Mobile:

Direct:

+49 151 / 638 646 73

+49 7335 / 186 999 21

Fax:
+49 7335 / 186 999 1






synapticon.com   |
@synapticon_co

Synapticon GmbH  |  Hohlbachweg 2  |  73344 Gruibingen, DE
Secretary +49 7335 / 186 999 0  |  General Manager: Nikolai Ensslen
Registry Court Ulm HRB 725114  |  USt-ID DE271647127

This message and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are addressed.
Please notify the sender immediately if you have received this e-mail by
mistake and delete it from your system.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add modphp

[Spenner]

Hi!

I am trying to add modphp to my image and always seem to get
 the same build error;

ERROR: Task 2693
(/home/gw/sources/meta-openembedded/meta-oe/recipes-support/
mysql/mariadb-native_5.1.67.bb,do_compile) failed with exit code '1'

I can add the apache2 package and the image will build and work fine but
when I add modphp in the same fashion, i get the build error above.

Is there any dependencies for modphp that I could be missing? 

Thanks for any insight!


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wrong version of busybox after adding new layers.

[Edward Vidal]

Hello,
Gary Thomas recommended that I do a refresh meta-oe.
I did git pull on poky & meta-oe.both of these are dylan branch
poky
commit 4e399f08d596197859214fdb3b06403b87bf8789
Author: Chen Qi 
Date:   Fri Aug 30 10:31:42 2013 +0800
meta-oe
commit 44754206632dd5b0725aeb43e99e4ff9e0245dca
Author: Javier Viguera 
Date:   Thu Sep 5 14:49:01 2013 +

now with MACHINE=beagleboard bitbake core-image-sato I am getting the
following error.
 ERROR: Task 3660
(virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/
dbus-glib_0.100.2.bb, do_compile) failed with exit code '1'

My last successful build was
poky
commit 64273e53f2789d2ea8393fc80909ac7086f168a7
Author: Peter Kjellerstedt 
Date:   Mon Jul 8 10:17:51 2013 +0100
meta-oe
commit ed84e64d22400595b68da4e75b48ab7ecc342aa9
Author: Martin Jansa 
Date:   Tue Jun 11 18:44:22 2013 +0200
When I try a build on my custom-image (added packages to
core-image-sato-sdk) I get the following errors.
ERROR: Task 5762
(virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/
dbus-glib_0.100.2.bb, do_compile) failed with exit code '1'
ERROR: Function failed: do_compile (see
/home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952
for further information)
ERROR: Logfile of failure stored in:
/home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952



Any and all help will be appreciated.
thanks


On Sun, Nov 17, 2013 at 5:17 PM, Edward Vidal wrote:

> Hello,
> MACHINE=zedboard bitbake core-image-sato builds okay.
>
> Build Configuration:
> BB_VERSION= "1.19.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Fedora-18"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "zedboard"
> DISTRO= "poky"
> DISTRO_VERSION= "1.4+snapshot-20131117"
> TUNE_FEATURES = " armv7a vfp neon zynq"
> TARGET_FPU= "vfp-neon"
> meta
> meta-yocto= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
> meta-xilinx
> meta-kc705
> meta-zc702
> meta-zedboard = "wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff"
> meta-yocto-bsp= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
>
> NOTE: Running noexec task 5589 of 5595 (ID: 3428,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/
> gst-meta-base_0.10.bb, do_build)
> NOTE: Running noexec task 5590 of 5595 (ID: 3103,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/
> gst-plugins-good_0.10.31.bb, do_build)
> NOTE: Running noexec task 5591 of 5595 (ID: 2804,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/owl-video-widget/
> libowl-av_git.bb, do_build)
> NOTE: Running noexec task 5592 of 5595 (ID: 1583,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/gaku/
> gaku_git.bb, do_build)
> NOTE: Running noexec task 5593 of 5595 (ID: 313,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/packagegroups/
> packagegroup-core-x11-sato.bb, do_build)
> NOTE: Running task 5594 of 5595 (ID: 7,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/
> core-image-sato.bb, do_rootfs)
> NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Started
> NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Succeeded
> NOTE: Running noexec task 5595 of 5595 (ID: 12,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/
> core-image-sato.bb, do_build)
> NOTE: Tasks Summary: Attempted 5595 tasks of which 404 didn't need to be
> rerun and all succeeded.
>
> busybox:
>   meta 1.21.1
> was used.
>
> After adding these 2 lines to bblayers.conf
>   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe \
>   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia \
>
> bitbake-layers show-layers
> layer path  priority
> ==
> meta  /home/vidal/POKY/build111613_zedboard/poky/meta  5
> meta-yocto
> /home/vidal/POKY/build111613_zedboard/poky/meta-yocto  5
> meta-oe
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe  6
> meta-multimedia
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia  6
> meta-xilinx
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx  8
> meta-kc705
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-kc705  8
> meta-zc702
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zc702  8
> meta-zedboard
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zedboard  8
> meta-yocto-bsp
> /home/vidal/POKY/build111613_zedboard/poky/meta-yocto-bsp  5
> [vidal@ws009 build]$ bitbake-layers show-recipes
> Parsing recipes..ERROR: No recipes available for:
>
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
> What is the procedure to us busybox_1.20.2 

Re: [yocto] How to add modphp

[Martin Jansa]

On Mon, Nov 18, 2013 at 07:23:28PM +, Spenner wrote:
> Hi!
> 
> I am trying to add modphp to my image and always seem to get
>  the same build error;
> 
> ERROR: Task 2693
> (/home/gw/sources/meta-openembedded/meta-oe/recipes-support/
> mysql/mariadb-native_5.1.67.bb,do_compile) failed with exit code '1'

read log.do_compile, hard to say what went wrong when you don't share
any details

> I can add the apache2 package and the image will build and work fine but
> when I add modphp in the same fashion, i get the build error above.
> 
> Is there any dependencies for modphp that I could be missing? 
> 
> Thanks for any insight!
> 
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] Using the camera

[Gary Thomas]

I have the raspberrypi camera (the one that plugs directly into
the board) running with Raspbian.  Now I'd like to have it working
with my Yocto based build.  I'm running the latest kernel which I
think matches the same kernel on Raspbian and I copied the /boot/config.txt
from my Raspbian disk to my Yocto image which I think should enable the
camera.  I've also checked the kernel cmdline which I think matches.

However, when I try to access the camera I get this error:
  root@raspberrypi:~# raspistill  -o /tmp/xx.jpg
  mmal: mmal_component_create_core: could not find component 'vc.ril.camera'
  mmal: Failed to create camera component
  mmal: main: Failed to create camera component
  mmal: Failed to run camera app. Please check for firmware updates

Any ideas what I need to do to get the camera working?

Thanks

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Using the camera

[Philipp Wagner]

Am 18.11.2013 21:37, Gary Thomas wrote:
> I have the raspberrypi camera (the one that plugs directly into
> the board) running with Raspbian.  Now I'd like to have it working
> with my Yocto based build.  I'm running the latest kernel which I
> think matches the same kernel on Raspbian and I copied the /boot/config.txt
> from my Raspbian disk to my Yocto image which I think should enable the
> camera.  I've also checked the kernel cmdline which I think matches.
> 
> However, when I try to access the camera I get this error:
>   root@raspberrypi:~# raspistill  -o /tmp/xx.jpg
>   mmal: mmal_component_create_core: could not find component
> 'vc.ril.camera'
>   mmal: Failed to create camera component
>   mmal: main: Failed to create camera component
>   mmal: Failed to run camera app. Please check for firmware updates
> 
> Any ideas what I need to do to get the camera working?

Did you also check that you are using the latest firmware (i.e. a quite
recent checkout of meta-raspberrypi)? I don't have the camera myself, so
I've never tested this feature.

Philipp
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] RFC 500 line media config fragment

[Hart, Darren]

Bruce,

I've been carrying around a 500 line config fragment from Koen for the
MinnowBoard that I would like to eliminate from the BSP.

The time to validate these options will be significant, so before I dig
in, I'm wondering what we think the best way to deal with these
internally to linux-yocto.

This fragment enables media APIs, subsystems, webcams, analog and
digital TV tuners, etc. I imagine there is sum commonality here that
could go in a media-common fragment, like VIDEO_V4L2, etc. A webcam
fragment would be logical (do we break that out into USB, PCI, SoC?),
what about tuners? digital, analog, satellite, terrestrial, USB, PCI...
lots of ways to split it. We didn't split by bus on the wifi features,
so the logical split to me would be:

media-common.cfg
webcam.cfg
tuner.cfg

Possibly with something like:

media-soc.cfg for some of the more specific stuff - or perhaps just
eliminate those and rely on the BSP for that SoC to pull those in?
Yeah... that I think.

media.cfg attached. Any other suggestions?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

++ .config  2013-04-19 11:55:51.013419546 +0200
CONFIG_FW_LOADER=m
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_ALTERA_STAPL=m
CONFIG_MFD_WL1273_CORE=m
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_MEDIA_RC_SUPPORT=y
CONFIG_MEDIA_CONTROLLER=y
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_SUBDEV_API=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_TUNER=m
CONFIG_V4L2_MEM2MEM_DEV=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_DMA_CONTIG=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_DVB_CORE=y
CONFIG_DVB_NET=y
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_DYNAMIC_MINORS=y
CONFIG_RC_CORE=y
CONFIG_RC_MAP=y
CONFIG_RC_DECODERS=y
CONFIG_LIRC=m
CONFIG_IR_LIRC_CODEC=m
CONFIG_IR_NEC_DECODER=y
CONFIG_IR_RC5_DECODER=y
CONFIG_IR_RC6_DECODER=y
CONFIG_IR_JVC_DECODER=y
CONFIG_IR_SONY_DECODER=y
CONFIG_IR_RC5_SZ_DECODER=y
CONFIG_IR_SANYO_DECODER=y
CONFIG_IR_MCE_KBD_DECODER=y
# CONFIG_RC_DEVICES is not set
CONFIG_MEDIA_USB_SUPPORT=y

#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_BENQ=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_CPIA1=m
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_JL2005BCD=m
CONFIG_USB_GSPCA_KINECT=m
CONFIG_USB_GSPCA_KONICA=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_NW80X=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_OV534_9=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7302=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SE401=m
CONFIG_USB_GSPCA_SN9C2028=m
CONFIG_USB_GSPCA_SN9C20X=m
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SPCA1528=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_SQ930X=m
CONFIG_USB_GSPCA_STK014=m
CONFIG_USB_GSPCA_STV0680=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TOPRO=m
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_VICAM=m
CONFIG_USB_GSPCA_XIRLINK_CIT=m
CONFIG_USB_GSPCA_ZC3XX=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
CONFIG_VIDEO_CPIA2=m
# CONFIG_USB_ZR364XX is not set
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
CONFIG_USB_SN9C102=m

#
# Analog TV USB devices
#
CONFIG_VIDEO_AU0828=m
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
CONFIG_VIDEO_TLG2300=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_STK1160=m
# CONFIG_VIDEO_STK1160_AC97 is not set

#
# Analog/digital TV USB devices
#
CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_RC=y
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
CONFIG_VIDEO_TM6000=m
CONFIG_VIDEO_TM6000_ALSA=m
CONFIG_VIDEO_TM6000_DVB=m

#
# Digital TV USB devices
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_USB_PCTV452E=m
CONFIG_DVB_USB_DW2102=m
CONFIG_DVB_USB_CINERGY_T2=m
CONFIG_DVB_USB_DTV5100=m
CONFIG_DVB_USB_FRIIO=m
CONFIG_DVB_USB_AZ6027=m
CONFIG_DVB_USB_TECHNISAT_USB2=m
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_CYPRESS

Re: [yocto] How to add modphp

[Gary Thomas]

On 2013-11-18 12:23, Spenner wrote:

Hi!

I am trying to add modphp to my image and always seem to get
  the same build error;

ERROR: Task 2693
(/home/gw/sources/meta-openembedded/meta-oe/recipes-support/
mysql/mariadb-native_5.1.67.bb,do_compile) failed with exit code '1'

I can add the apache2 package and the image will build and work fine but
when I add modphp in the same fashion, i get the build error above.


More information about this error is needed to help figure out the problem.
Bitbake should have printed the last few lines of the error log which you
could paste here for us to see.  Alternatively, the complete log is at
  .../tmp/work/x86_64-linux/mariadb-native/5.1.67/temp/log.do_compile
 -or-
  .../tmp/work/i686-linux/mariadb-native/5.1.67/temp/log.do_compile



Is there any dependencies for modphp that I could be missing?

Thanks for any insight!


BTW, I just built this on my Ubuntu 12.04/x86_64 with no problems.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Using the camera

[Gary Thomas]

On 2013-11-18 14:10, Philipp Wagner wrote:

Am 18.11.2013 21:37, Gary Thomas wrote:

I have the raspberrypi camera (the one that plugs directly into
the board) running with Raspbian.  Now I'd like to have it working
with my Yocto based build.  I'm running the latest kernel which I
think matches the same kernel on Raspbian and I copied the /boot/config.txt
from my Raspbian disk to my Yocto image which I think should enable the
camera.  I've also checked the kernel cmdline which I think matches.

However, when I try to access the camera I get this error:
   root@raspberrypi:~# raspistill  -o /tmp/xx.jpg
   mmal: mmal_component_create_core: could not find component
'vc.ril.camera'
   mmal: Failed to create camera component
   mmal: main: Failed to create camera component
   mmal: Failed to run camera app. Please check for firmware updates

Any ideas what I need to do to get the camera working?


Did you also check that you are using the latest firmware (i.e. a quite
recent checkout of meta-raspberrypi)? I don't have the camera myself, so
I've never tested this feature.


I do have the very latest version of meta-raspberrypi, with the 20131113
version of the firmware (bcm bootfiles).

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wrong version of busybox after adding new layers.

[Edward Vidal]

Hello,
This is the first time that I have used the git bisect.  I hope this helps
git bisect start
git bisect good 64273e53f2789d2ea8393fc80909ac7086f168a7
git bisect bad 4e399f08d596197859214fdb3b06403b87bf8789
secting: 43 revisions left to test after this (roughly 6 steps)
[7a3b4c55410b49a02945c72b554102a483095405] gst-plugins-base: add missing
dependency on glib-2.0-native

git bisect bad
Bisecting: 21 revisions left to test after this (roughly 5 steps)
[b4ba3269102424b614d91ca8be10501176042f62] external-sourcery: add missing
providers

git bisect bad
Bisecting: 10 revisions left to test after this (roughly 3 steps)
[4d47a1e6445b2a4839bae7c3ba8fa69f1b32f602] gst-plugins-good: add
PACKAGECONFIG for jack

git bisect bad
Bisecting: 4 revisions left to test after this (roughly 2 steps)
[dea3e6964949c2d7269570d2f19c74033e54200e] mesa: fix EGL compilation
without X11 headers

git bisect isecting: 2 revisions left to test after this (roughly 1 step)
[d6d12689c0628f11a282c2b54ebcb8aa3ab8c673] populate_sdk_base: fix bashism

git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[eb5ec8899d41d2df7fb9d9918d2d93042a678d97] populate_sdk_base,
adt_installer: abort install if path contains spaces

git bisect bad
eb5ec8899d41d2df7fb9d9918d2d93042a678d97 is the first bad commit
commit eb5ec8899d41d2df7fb9d9918d2d93042a678d97
Author: Laurentiu Palcu 
Date:   Tue Jun 25 14:59:05 2013 +0300

populate_sdk_base, adt_installer: abort install if path contains spaces

Spaces are not handled properly in some parts of oe-core and it's safer
to abort toolchain installation if path contains spaces. Even though
we fix space handling in the toolchain installation script, there are
various other parts in the toolchain (perl scripts, sysroot path passed
to
toolchain binaries, shebang lines) that would need special handling. So,
for now, just bail out if path contains spaces.

The checking for spaces in the path is done after expanding relative
paths to absolute and tilde conversion.

[YOCTO #4488]
(From OE-Core master rev: 8c35ba2d3048ce69f74f72cb2676e4bc162cfb63)

(From OE-Core rev: 407e57879ea2f931bff32993b850c9d59d228303)

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie 

:04 04 d48370d500ce89a9b3ba7194b5e5beda216a926d
db610074307067f3882a9faabb342fe2a541 M  meta
I hope this helps.
As always all help is appreciated.
Thanks


On Mon, Nov 18, 2013 at 1:09 PM, Edward Vidal wrote:

> Hello,
> Gary Thomas recommended that I do a refresh meta-oe.
> I did git pull on poky & meta-oe.both of these are dylan branch
> poky
> commit 4e399f08d596197859214fdb3b06403b87bf8789
> Author: Chen Qi 
> Date:   Fri Aug 30 10:31:42 2013 +0800
> meta-oe
> commit 44754206632dd5b0725aeb43e99e4ff9e0245dca
> Author: Javier Viguera 
> Date:   Thu Sep 5 14:49:01 2013 +
>
> now with MACHINE=beagleboard bitbake core-image-sato I am getting the
> following error.
>  ERROR: Task 3660
> (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/
> dbus-glib_0.100.2.bb, do_compile) failed with exit code '1'
>
> My last successful build was
> poky
> commit 64273e53f2789d2ea8393fc80909ac7086f168a7
> Author: Peter Kjellerstedt 
> Date:   Mon Jul 8 10:17:51 2013 +0100
> meta-oe
> commit ed84e64d22400595b68da4e75b48ab7ecc342aa9
> Author: Martin Jansa 
> Date:   Tue Jun 11 18:44:22 2013 +0200
> When I try a build on my custom-image (added packages to
> core-image-sato-sdk) I get the following errors.
> ERROR: Task 5762
> (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/
> dbus-glib_0.100.2.bb, do_compile) failed with exit code '1'
> ERROR: Function failed: do_compile (see
> /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952
> for further information)
> ERROR: Logfile of failure stored in:
> /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952
>
>
>
> Any and all help will be appreciated.
> thanks
>
>
> On Sun, Nov 17, 2013 at 5:17 PM, Edward Vidal wrote:
>
>> Hello,
>> MACHINE=zedboard bitbake core-image-sato builds okay.
>>
>> Build Configuration:
>> BB_VERSION= "1.19.1"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING   = "Fedora-18"
>> TARGET_SYS= "arm-poky-linux-gnueabi"
>> MACHINE   = "zedboard"
>> DISTRO= "poky"
>> DISTRO_VERSION= "1.4+snapshot-20131117"
>> TUNE_FEATURES = " armv7a vfp neon zynq"
>> TARGET_FPU= "vfp-neon"
>> meta
>> meta-yocto= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
>> meta-xilinx
>> meta-kc705
>> meta-zc702
>> meta-zedboard = "wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff"
>> meta-yocto-bsp= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
>>
>> NOTE: Running noexec task 5589 of 5595 (ID: 3428,
>> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/
>> gst-met

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, November 19, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

[Liu, Song]

Agenda:

* Opens collection - 5 min (Song)
* Yocto 1.6 status - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.6_Status
  https://wiki.yoctoproject.org/wiki/Yocto_1.6_Features
* SWAT team rotation: Laurentiu Palcu -> Nitin
* Opens - 10 min
* Team Sharing - 20 min


-Original Appointment-


We encourage people attending the meeting to logon the Yocto IRC chancel during 
the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto
IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html

Conference details
Conference name:Yocto Project Technical Team
Conference date/start time: Tue Jun 25, 2013 at 11:00 AM Eastern Daylight 
Time (GMT-0400)
Participants:   30
Duration:   60 minutes
Participant passcode:   42001078
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 participant: 
1.972.995.x42001078#
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:
01908 355599

US:
972 995  or 1877 561 6828


Recurring conferences
First scheduled conference: Tue Jun 25, 2013
Recurrence frequency:   Weekly - Every 1 week(s) on Tuesday
Recurrence ends:End after 52 occurrences


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wrong version of busybox after adding new layers.

[Edward Vidal]

Hello
Still was getting error.  Thinking it might be my download area. Started
with a
clean down load area and new work area.
Build Configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard"
DISTRO= "poky"
DISTRO_VERSION= "1.4.2"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "dylan:4e399f08d596197859214fdb3b06403b87bf8789"
meta-oe
meta-multimedia   = "dylan:44754206632dd5b0725aeb43e99e4ff9e0245dca"
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = "dylan:cf9571203be0af5fc654952d3f00e0a7e0fb1174"
meta-yocto-bsp= "dylan:4e399f08d596197859214fdb3b06403b87bf8789"

ERROR: Function failed: Fetcher failure for URL: '
http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz'.
Unable to fetch URL from any source.

uhd-images_003.005.002-release.tar.gz_bad-checksum_2912c1c7cde099f2671f2f8f24879b82
Downloaded manually and in fact the md5sum is shown below

Can someone please pass to meta-oe since this site is currently blocked to
new u
sers.
md5sum uhd-images_003.005.002-release.tar.gz

2912c1c7cde099f2671f2f8f24879b82  uhd-images_003.005.002-release.tar.gz
Any and all help is appreciated.
Thanks


On Mon, Nov 18, 2013 at 4:10 PM, Edward Vidal wrote:

> Hello,
> This is the first time that I have used the git bisect.  I hope this helps
> git bisect start
> git bisect good 64273e53f2789d2ea8393fc80909ac7086f168a7
> git bisect bad 4e399f08d596197859214fdb3b06403b87bf8789
> secting: 43 revisions left to test after this (roughly 6 steps)
> [7a3b4c55410b49a02945c72b554102a483095405] gst-plugins-base: add missing
> dependency on glib-2.0-native
>
> git bisect bad
> Bisecting: 21 revisions left to test after this (roughly 5 steps)
> [b4ba3269102424b614d91ca8be10501176042f62] external-sourcery: add missing
> providers
>
> git bisect bad
> Bisecting: 10 revisions left to test after this (roughly 3 steps)
> [4d47a1e6445b2a4839bae7c3ba8fa69f1b32f602] gst-plugins-good: add
> PACKAGECONFIG for jack
>
> git bisect bad
> Bisecting: 4 revisions left to test after this (roughly 2 steps)
> [dea3e6964949c2d7269570d2f19c74033e54200e] mesa: fix EGL compilation
> without X11 headers
>
> git bisect isecting: 2 revisions left to test after this (roughly 1 step)
> [d6d12689c0628f11a282c2b54ebcb8aa3ab8c673] populate_sdk_base: fix bashism
>
> git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [eb5ec8899d41d2df7fb9d9918d2d93042a678d97] populate_sdk_base,
> adt_installer: abort install if path contains spaces
>
> git bisect bad
> eb5ec8899d41d2df7fb9d9918d2d93042a678d97 is the first bad commit
> commit eb5ec8899d41d2df7fb9d9918d2d93042a678d97
> Author: Laurentiu Palcu 
> Date:   Tue Jun 25 14:59:05 2013 +0300
>
> populate_sdk_base, adt_installer: abort install if path contains spaces
>
> Spaces are not handled properly in some parts of oe-core and it's safer
> to abort toolchain installation if path contains spaces. Even though
> we fix space handling in the toolchain installation script, there are
> various other parts in the toolchain (perl scripts, sysroot path
> passed to
> toolchain binaries, shebang lines) that would need special handling.
> So,
> for now, just bail out if path contains spaces.
>
> The checking for spaces in the path is done after expanding relative
> paths to absolute and tilde conversion.
>
> [YOCTO #4488]
> (From OE-Core master rev: 8c35ba2d3048ce69f74f72cb2676e4bc162cfb63)
>
> (From OE-Core rev: 407e57879ea2f931bff32993b850c9d59d228303)
>
> Signed-off-by: Laurentiu Palcu 
> Signed-off-by: Richard Purdie 
>
> :04 04 d48370d500ce89a9b3ba7194b5e5beda216a926d
> db610074307067f3882a9faabb342fe2a541 M  meta
> I hope this helps.
> As always all help is appreciated.
> Thanks
>
>
> On Mon, Nov 18, 2013 at 1:09 PM, Edward Vidal wrote:
>
>> Hello,
>> Gary Thomas recommended that I do a refresh meta-oe.
>> I did git pull on poky & meta-oe.both of these are dylan branch
>> poky
>> commit 4e399f08d596197859214fdb3b06403b87bf8789
>> Author: Chen Qi 
>> Date:   Fri Aug 30 10:31:42 2013 +0800
>> meta-oe
>> commit 44754206632dd5b0725aeb43e99e4ff9e0245dca
>> Author: Javier Viguera 
>> Date:   Thu Sep 5 14:49:01 2013 +
>>
>> now with MACHINE=beagleboard bitbake core-image-sato I am getting the
>> following error.
>>  ERROR: Task 3660
>> (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/
>> dbus-glib_0.100.2.bb, do_compile) failed with exit code '1'
>>
>> My last successful build was
>> poky
>> commit 64273e53f2789d2ea8393fc80909ac7086f168a7
>> Author: Peter Kjellerstedt 
>> Date:   Mon Jul 8 10:17:51 2013 +0100
>> meta-oe
>> commit ed84e64d22400595b68da4e75b48ab7ecc342aa9
>> Author: Martin Jansa 
>> Date:   Tue Jun 11 18:44:22 2013 +0200
>> When I try

Re: [yocto] wrong version of busybox after adding new layers.

[Edward Vidal]

Hello,
This fixed 1 error. Please pass to meta-oe group
git diff
diff --git a/meta-oe/recipes-connectivity/uhd/uhd-firmware_003.005.002.bbb/meta
index 3afae27..7fc0574 100644
--- a/meta-oe/recipes-connectivity/uhd/uhd-firmware_003.005.002.bb
+++ b/meta-oe/recipes-connectivity/uhd/uhd-firmware_003.005.002.bb
@@ -9,8 +9,8 @@ LIC_FILES_CHKSUM = "file://share/uhd/images/
usrp_e100_fpga_v2.bi
 inherit allarch

 SRC_URI = "
http://files.ettus.com/binaries/uhd_stable/releases/uhd_${PV}-releas
-SRC_URI[md5sum] = "2dbb7e2fb0c774e5ea2372bac25102e5"
-SRC_URI[sha256sum] =
"217efa814fb031ad136bd3dcf89ca219dd6d7ee01aa7e65c56c56b773
+SRC_URI[md5sum] = "2912c1c7cde099f2671f2f8f24879b82"
+SRC_URI[sha256sum] =
"6c3c70158e74754f29d9709a7668eff6238a5cd5bf31e35b31bbeaaee

 S = "${WORKDIR}/uhd-images_${PV}-release
I still have several ERRORS will continue in the morning trying to find
fixes
Any and all help will be appreciated
Thanks


On Sun, Nov 17, 2013 at 5:17 PM, Edward Vidal wrote:

> Hello,
> MACHINE=zedboard bitbake core-image-sato builds okay.
>
> Build Configuration:
> BB_VERSION= "1.19.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Fedora-18"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "zedboard"
> DISTRO= "poky"
> DISTRO_VERSION= "1.4+snapshot-20131117"
> TUNE_FEATURES = " armv7a vfp neon zynq"
> TARGET_FPU= "vfp-neon"
> meta
> meta-yocto= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
> meta-xilinx
> meta-kc705
> meta-zc702
> meta-zedboard = "wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff"
> meta-yocto-bsp= "wkg:3dee534f1e25109e0bdb681de0746c336f4b8840"
>
> NOTE: Running noexec task 5589 of 5595 (ID: 3428,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/
> gst-meta-base_0.10.bb, do_build)
> NOTE: Running noexec task 5590 of 5595 (ID: 3103,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/
> gst-plugins-good_0.10.31.bb, do_build)
> NOTE: Running noexec task 5591 of 5595 (ID: 2804,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/owl-video-widget/
> libowl-av_git.bb, do_build)
> NOTE: Running noexec task 5592 of 5595 (ID: 1583,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/gaku/
> gaku_git.bb, do_build)
> NOTE: Running noexec task 5593 of 5595 (ID: 313,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/packagegroups/
> packagegroup-core-x11-sato.bb, do_build)
> NOTE: Running task 5594 of 5595 (ID: 7,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/
> core-image-sato.bb, do_rootfs)
> NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Started
> NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Succeeded
> NOTE: Running noexec task 5595 of 5595 (ID: 12,
> /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/
> core-image-sato.bb, do_build)
> NOTE: Tasks Summary: Attempted 5595 tasks of which 404 didn't need to be
> rerun and all succeeded.
>
> busybox:
>   meta 1.21.1
> was used.
>
> After adding these 2 lines to bblayers.conf
>   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe \
>   /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia \
>
> bitbake-layers show-layers
> layer path  priority
> ==
> meta  /home/vidal/POKY/build111613_zedboard/poky/meta  5
> meta-yocto
> /home/vidal/POKY/build111613_zedboard/poky/meta-yocto  5
> meta-oe
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe  6
> meta-multimedia
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia  6
> meta-xilinx
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx  8
> meta-kc705
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-kc705  8
> meta-zc702
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zc702  8
> meta-zedboard
> /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zedboard  8
> meta-yocto-bsp
> /home/vidal/POKY/build111613_zedboard/poky/meta-yocto-bsp  5
> [vidal@ws009 build]$ bitbake-layers show-recipes
> Parsing recipes..ERROR: No recipes available for:
>
> /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
> What is the procedure to us busybox_1.20.2 with the new layers?
> Any and all help is appreciated.
> Thanks
>
>
>
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?

[Jack Lemon]

It wasn't any help??!! really??!!


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto