Re: [yocto] Missing or unbuildable dependency chain

[Josef Holzmayr]

Hi,

On 17.03.2017 06:22, ravikiran j wrote:

ERROR: Nothing RPROVIDES 'dnsmasq'


meta-networking does, as to be found 
through:https://layers.openembedded.org/layerindex/recipe/4473/


Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

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

Re: [yocto] [qa-tools][PATCH] full-test-cycle-wrapper: Correct qemu-auto variables

[Jussi Kukkonen]

On 16 March 2017 at 17:34,  wrote:
>
> From: Jose Perez Carranza 
>
> Update variables for creating test runs for qemu ato component
>
> Signed-off-by: Jose Perez Carranza 
> ---
>  scripts/full-test-cycle-wrapper.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/full-test-cycle-wrapper.sh
b/scripts/full-test-cycle-wrapper.sh
> index f52cd96..3a6ba0f 100755
> --- a/scripts/full-test-cycle-wrapper.sh
> +++ b/scripts/full-test-cycle-wrapper.sh
> @@ -82,8 +82,8 @@ create_yocto(){
> create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
>
> #QEMUs Autos
> -   EVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64"
"qemuppc" "qemux86-64" "qemux86-lsb" "qemux86_64-lsb")
> -   ECUTION_TYPE="AUTO"
> +   ENVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" "qemumips64"
"qemuppc" "qemux86-64")

It seems this is in master already so I'll just mention the typo for
future: ENVIRONMETS should probably be ENVIRONMENTS in whole file.

  Jussi

> +   EXECUTION_TYPE="AUTO"
> create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
>
> #QEMUs Autos LSB
> --
> 2.11.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] epiphany for wayland only environemnt?

[Takashi Matsuzawa]

Hello, Yocto.


I have looked into recipes index, etc. but I so far I could not figure out 
clear answer, so if you have status on this, I highly appreciate.


I am looking for a web browser that can (without much effort) be built and run 
on Yocto based environment, with wayland-only window system (without x11 
libraries).


i.e. if such Yocto recipe already exist, it would be a great help.

I can see midori, epiphay, or other browser 'should run' on wayland 
environment, but it seems they rely graphics libraries that still depends on 
x11 and in Yocto recipes x11 DISTRO_FEATURES is being set as requirement for 
them.


Is this still the situation on latest master or morty branches.

If there is an attempt for the similar?

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

Re: [yocto] epiphany for wayland only environemnt?

[Burton, Ross]

On 17 March 2017 at 10:08, Takashi Matsuzawa  wrote:

> I can see midori, epiphay, or other browser 'should run' on wayland
> environment, but it seems they rely graphics libraries that still depends
> on x11 and in Yocto recipes x11 DISTRO_FEATURES is being set as requirement
> for them.
>
> The GNOME stack can mostly run under Wayland natively, so it should be
possible with a bit of tweaking to build Epiphany without X11.  You might
need to look at the pieces where x11 is marked as a requirement and see if
that's isn't true anymore, or if it can be made optional.

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

Re: [yocto] Missing or unbuildable dependency chain

[ravikiran j]

Hi,

Thank you for your reply,
Now i am able to build the packagegroup-core-extended based image.

But if add the *packagegroup-core-multimedia* in image recipe file,
I am getting similar error as above mentioned.

*ERROR: Nothing PROVIDES 'ffmpeg'* (but
/home/kamama-yocto/yocto/poky/meta-openembedded/meta-multimedia/recipes-multimedia/musicpd/
mpd_0.19.15.bb DEPENDS on or otherwise requires it)
ERROR: ffmpeg was skipped: because it has a restricted license not
whitelisted in LICENSE_FLAGS_WHITELIST
NOTE: Runtime target 'mpd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['mpd', 'ffmpeg']
NOTE: Runtime target 'xfmpc-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xfmpc-dev', 'mpd', 'ffmpeg']
NOTE: Runtime target 'xfmpc' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xfmpc', 'mpd', 'ffmpeg']
NOTE: Runtime target 'packagegroup-xfce-multimedia' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['packagegroup-xfce-multimedia', 'xfmpc', 'mpd', 'ffmpeg']
ERROR: Required build target 'core-image-minimal-xfce' has no buildable
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal-xfce',
'packagegroup-xfce-multimedia', 'xfmpc', 'mpd', 'ffmpeg']

for this error  which layer i needs to be added ?

Thanks and Regards,
Ravikiran


On Fri, Mar 17, 2017 at 1:00 PM, Josef Holzmayr <
holzm...@rsi-elektrotechnik.de> wrote:

> Hi,
>
> On 17.03.2017 06:22, ravikiran j wrote:
>
>> ERROR: Nothing RPROVIDES 'dnsmasq'
>>
>
> meta-networking does, as to be found through:https://layers.openemb
> edded.org/layerindex/recipe/4473/
>
> Greetz
> --
> Josef Holzmayr
> Software Developer Embedded Systems
>
> Tel: +49 8444 9204-48
> Fax: +49 8444 9204-50
>
> R-S-I Elektrotechnik GmbH & Co. KG
> Woelkestrasse 11
> D-85301 Schweitenkirchen
> www.rsi-elektrotechnik.de
> ———
> Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
> Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> Ust-IdNr: DE 128592548
>
> _
> Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
> Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> USt-IdNr.: DE 128592548
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing or unbuildable dependency chain

[Josef Holzmayr]

Hi.

On 17.03.2017 13:10, ravikiran j wrote:

for this error  which layer i needs to be added ?


As I already explicitly linked to the layerindex, here is another 
example of its usefulness:

https://layers.openembedded.org/layerindex/recipe/47350/

Please understand that I probably won't respond another time to things 
that are trivially solvable through information that I already provided.


Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

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

Re: [yocto] [qa-tools][PATCH] full-test-cycle-wrapper: Correct qemu-auto variables

[Jose Perez Carranza]

On 03/17/2017 03:47 AM, Jussi Kukkonen wrote:



On 16 March 2017 at 17:34, > wrote:

>
> From: Jose Perez Carranza >

>
> Update variables for creating test runs for qemu ato component
>
> Signed-off-by: Jose Perez Carranza 
>

> ---
>  scripts/full-test-cycle-wrapper.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/full-test-cycle-wrapper.sh 
b/scripts/full-test-cycle-wrapper.sh

> index f52cd96..3a6ba0f 100755
> --- a/scripts/full-test-cycle-wrapper.sh
> +++ b/scripts/full-test-cycle-wrapper.sh
> @@ -82,8 +82,8 @@ create_yocto(){
> create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
>
> #QEMUs Autos
> -   EVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" 
"qemumips64" "qemuppc" "qemux86-64" "qemux86-lsb" "qemux86_64-lsb")

> -   ECUTION_TYPE="AUTO"
> +   ENVIRONMETS=("qemu-x86" "qemuarm" "qemuarm64" "qemumips" 
"qemumips64" "qemuppc" "qemux86-64")


It seems this is in master already so I'll just mention the typo for 
future: ENVIRONMETS should probably be ENVIRONMENTS in whole file.
I'll correct that in the next series of patches. thanks for pointing it 
out.


José


  Jussi

> +   EXECUTION_TYPE="AUTO"
> create_test_run "${1}" "core-image-sato-sdk_ANYQEMU"
>
> #QEMUs Autos LSB
> --
> 2.11.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto


--
Saludos
José

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

[yocto] [PATCH 1/1][meta-intel][rmc] rmc: update SRCREV for rmc recipe

[Todor Minchev]

This SRCREV adds fingerprint and database extraction functionality to RMC

Extract database:
rmc -E -d rmc.db -o output/directory/

Extract fingerprint:
rmc -E -f fingerprint_file

https://bugzilla.yoctoproject.org/show_bug.cgi?id=10092

Signed-off-by: Todor Minchev 
---
 common/recipes-bsp/rmc/rmc.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/recipes-bsp/rmc/rmc.bb b/common/recipes-bsp/rmc/rmc.bb
index f5c648d..b4eb0ef 100644
--- a/common/recipes-bsp/rmc/rmc.bb
+++ b/common/recipes-bsp/rmc/rmc.bb
@@ -14,7 +14,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=838c366f69b72c5df05c96dff79b35f2"

 SRC_URI = "git://git.yoctoproject.org/rmc"

-SRCREV = "4799cb89b543712390d863a6fc50a58881590fa2"
+SRCREV = "d28eaec425f05511f0d9cd82b3623e95980ff2f6"

 S = "${WORKDIR}/git"

--
2.12.0

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

Re: [yocto] [meta-intel] Installing a Yocto image to emmc

[Trevor Woerner]

On Fri 2017-03-17 @ 11:19:30 PM, Duran, Randy G wrote:
> Hello, I am trying to get information on software or procedure to flash
> a Yocto image on to a Joule's emmc not using normal steps such using a
> bootlable USB nor sdcard. I am attempting to automate flashing an image
> on to device without any human interventions. I am looking for something
> like Platform/Phone flash tool software equivalent for android devices. Any
> information is appreciated.

Flashing to a board's eMMC instantly puts you into "vendor-specific" country.
Each vendor/board will have its own way of doing it, usually involving vendor
specific software/protocols. If you're lucky the vendor will have implemented
android's fastboot, which makes it more or less non-vendor-specific, unless,
of course, they don't really implement it properly... ;-)

Newer versions of u-boot have fastboot support, so, if enabled, you can
sometimes flash via u-boot.

The toughest part about flashing to eMMC is the procedure required to put the
board into the mode to accept flashing to its eMMC.

The dragonboard, for example, requires you to hold down the "volume down"
button while rebooting, then you can use fastboot. Do you have an easy way to
automate holding down the volume down button while rebooting?

The firefly requires you to hold down the RECOVERY button while pressing the
RESET button. Or you can just use "dd" from within Linux to zero the first
couple sectors of /dev/mmcblk2, then reboot. The protocol to flash its eMMC is
something they came up with, but I think they recently released that code (I
haven't looked at it yet).

It's been a while since I've used a BBB but the last time I checked, one would
create an image using OE and in that image would be an eMMC payload. Once
booting into Linux you'd then write the payload to the eMMC. Not sure if
there's a way to do it "offline".

So if you're working with the Joule, you'll have to find its way of flashing
its eMMC. Hopefully you know someone who works at Intel who can help with the
specifics... ;-)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Installing a Yocto image to emmc

[Duran, Randy G]

Hello, I am trying to get information on software or procedure to flash a Yocto 
image on to a Joule's emmc not using normal steps such using a bootlable USB 
nor sdcard. I am attempting to automate flashing an image on to device without 
any human interventions. I am looking for something like Platform/Phone flash 
tool software equivalent for android devices. Any information is appreciated.

Thanks,

-Randy

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

[yocto] [meta-rockchip][PATCH] machine: rk3288: don't hard-code kernel choice

[Trevor Woerner]

Allow the user to ultimately choose the kernel. Make 'linux' the _preferred_,
not the _required_.

Signed-off-by: Trevor Woerner 
---
 conf/machine/include/rk3288.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index 964d8b0..88acbbf 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -6,7 +6,7 @@ SOC_FAMILY = "rk3288"
 require conf/machine/include/tune-cortexa17.inc
 require conf/machine/include/soc-family.inc
 
-PREFERRED_PROVIDER_virtual/kernel = "linux"
+PREFERRED_PROVIDER_virtual/kernel ?= "linux"
 SERIAL_CONSOLES = "115200;ttyS2"
 KERNEL_IMAGETYPE = "zImage"
 KBUILD_DEFCONFIG = "multi_v7_defconfig"
-- 
2.12.0.rc1.48.g076c053

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