[yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"

2018-05-17 Thread Steve Pavao 
I am trying to build for raspberrypi3 near head of sumo. I get the following 
troublesome warning fairly often since I started doing some builds in sumo and 
master the past week.:

WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept 
hook 'update_gio_module_cache-nativesdk' failed, details in 
/data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk

Here is the detail of the warning is.  It basically reports "Invalid ELF image 
for this architecture":

NOTE: > Executing update_gio_module_cache-nativesdk intercept ...
WARNING: The postinstall intercept hook 'update_gio_module_cache-nativesdk' 
failed, details in /data/development/lfs/yocto/build/spark/raspb
errypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk
NOTE: Exit code 255. Output:
/data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/sdk/image/opt/poky/2
.5/sysroots/x86_64-pokysdk-linux/usr/libexec/nativesdk-gio-querymodules: 
Invalid ELF image for this architecture

Question: How serious is this warning, and what should I do about it?

- Steve Pavao
Korg R&D

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

Re: [yocto] [OE-core] [RFT] GCC 8.1

2018-05-17 Thread Martin Jansa 
On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused 
> > > this, it build OK with sumo since the -std=gnu99 addition.
> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated 
> > > before the last format character [-Werror=format-truncation=]
> > >               "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$",
> > >               ^~~
> > > 
> > 
> > something new, I will look into reproducing this.

The fix from you worked for me, thanks!

> > > I didn't get very far in testing, because our old kernel fails to build 
> > > with gcc8 and there are some other issues caused by other master 
> > > changes. But it doesn't look too bad (in my small test, lets see what 
> > > bitbake world will show), thanks a lot for new gcc.
> > > 
> > 
> > yes, older kernel needs fixes, especially to disable new warnings.
> > the mips/ppc fixes that I put out there might be helpful to cook up 
> > fixes for older kernels if running into same issues.
> 
> In this case it fails with Error: .err encountered for many drivers. It's not 
> the same case as in:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325615.html
> nor arm version of this change, both are already applied in our
> 4.4.3 based kernel.
> 
> I've tried to reproduce with vanilla 4.4.143 and it doesn't fail like this, 
> vanilla 4.4.3 doesn't
> fail, so it's caused by one of our 1 commits on top of 4.4.3 or the 
> config, need to dig a bit more.

Just FYI if someone needs similar fix, backporting this:
https://patchwork.kernel.org/patch/9170055/

fixed the issue for me, now I have successful kernel build.

The failing code was always in put_user calls, e.g. kernel/exit.s was showing:
@ 1581 "kernel-source/kernel/exit.c" 1
.ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; 
.ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; 
.ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; 
.ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif
bl  __put_user_4
@ 0 "" 2

with the error triggered on the middle line.
/tmp/ccHq8ugv.s: Assembler messages:
/tmp/ccHq8ugv.s:1179: Error: .err encountered
/tmp/ccHq8ugv.s:1331: Error: .err encountered
/tmp/ccHq8ugv.s:4617: Error: .err encountered
/tmp/ccHq8ugv.s:6222: Error: .err encountered
/tmp/ccHq8ugv.s:8705: Error: .err encountered
/tmp/ccHq8ugv.s:14486: Error: .err encountered
/tmp/ccHq8ugv.s:14646: Error: .err encountered
/tmp/ccHq8ugv.s:14806: Error: .err encountered
/tmp/ccHq8ugv.s:14966: Error: .err encountered
/tmp/ccHq8ugv.s:15126: Error: .err encountered
/tmp/ccHq8ugv.s:15286: Error: .err encountered

That leaves only few issues in our internal components and strange failure with 
perf which fails to include various header files:
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: 
../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: 
../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: 
../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: 
../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: 
../../../../include/uapi/linux/swab.h: No such file or directory
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26:
 error: #include nested too deeply
perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25:
 error: #include nested too deepl

Re: [yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"

2018-05-17 Thread Alexander Kanavin 

On 05/17/2018 12:17 PM, Steve Pavao wrote:

I am trying to build for raspberrypi3 near head of sumo. I get the following 
troublesome warning fairly often since I started doing some builds in sumo and 
master the past week.:

WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept 
hook 'update_gio_module_cache-nativesdk' failed, details in 
/data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk

Here is the detail of the warning is.  It basically reports "Invalid ELF image for 
this architecture":

NOTE: > Executing update_gio_module_cache-nativesdk intercept ...
WARNING: The postinstall intercept hook 'update_gio_module_cache-nativesdk' 
failed, details in /data/development/lfs/yocto/build/spark/raspb
errypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk
NOTE: Exit code 255. Output:
/data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/sdk/image/opt/poky/2
.5/sysroots/x86_64-pokysdk-linux/usr/libexec/nativesdk-gio-querymodules: 
Invalid ELF image for this architecture

Question: How serious is this warning, and what should I do about it?


Thanks for reporting! This is mostly harmless, but I'll make a patch to 
address it.


Alex

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

[yocto] Configuration network from qt5

2018-05-17 Thread Mauro Ziliani 

Hi all.

Which the betst choice to perform the network configuration in Yocto 
Krogoth from a qt5 application?


The configuration should be made without external script, using dbus.


Best regards,

  MZ

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

Re: [yocto] Configuration network from qt5

2018-05-17 Thread Mirza Krak 
On 17 May 2018 at 14:18, Mauro Ziliani  wrote:
> Hi all.
>
> Which the betst choice to perform the network configuration in Yocto Krogoth
> from a qt5 application?
>
> The configuration should be made without external script, using dbus.

Well you probably need to use a network manager that you can control
trough D-Bus. NetworkManager, ConnMan, systemd-networkd etc.

If you are using ConnMan you can use this:
https://git.merproject.org/mer-core/libconnman-qt

There might exist similar libraries for other network managers but I
am not aware of any.

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak
email: mi...@mkrak.org
web: https://mkrak.org
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] raspberrypi3 at head of sumo has broken console

2018-05-17 Thread Steve Pavao 
I just built raspberrypi3 at head of sumo.   The attached keyboard and mouse 
don’t work in the console, although a window and the prompt is displayed.  The 
mouse and keyboard work fine when booting Raspbian or other raspberrypi3 images 
I’ve built in other branches in the past.

Build info below:

parallels@ubuntu:/data/development/lfs/yocto/build/spark/raspberrypi3$ bitbake 
core-image-minimal
Parsing recipes: 100% 
|##|
 Time: 0:01:15
Parsing of 1935 .bb files complete (0 cached, 1935 parsed). 2790 targets, 120 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-16.04"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "raspberrypi3"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5"
TUNE_FEATURES= "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
cortexa7"
TARGET_FPU   = "hard"
meta 
meta-poky
meta-yocto-bsp   = "sumo:f0ec7c8b2dc1797ba22c45653a5f182b63354092"
meta-oe  
meta-python  
meta-multimedia  = "sumo:a19aa29f7fa336cd075b72c496fe1102e6e5422b"
meta-raspberrypi = "sumo:f2e2a4376e84dec6e5efeabaa86a4406fddf7dcd"

NOTE: Fetching uninative binary shim from 
http://downloads.yoctoproject.org/releases/uninative/1.9/x86_64-nativesdk-libc.tar.bz2;sha256sum=c26622a1f27dbf5b25de986b11584b5c5b2f322d9eb367f705a744f58a5561ec
Initialising tasks: 100% 
|###|
 Time: 0:00:03
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: libdaemon-0.14-r0 do_fetch: Failed to fetch URL 
http://0pointer.de/lennart/projects/libdaemon/libdaemon-0.14.tar.gz, attempting 
MIRRORS if available
WARNING: libnss-mdns-0.10-r7 do_fetch: Failed to fetch URL 
http://0pointer.de/lennart/projects/nss-mdns/nss-mdns-0.10.tar.gz, attempting 
MIRRORS if available
WARNING: apt-1.2.24-r0 do_fetch: Failed to fetch URL 
http://archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.2.24.tar.xz, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 5203 tasks of which 5 didn't need to be rerun 
and all succeeded.

Summary: There were 3 WARNING messages shown.

- Steve Pavao
Korg R&D


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

Re: [yocto] Configuration network from qt5

2018-05-17 Thread Mauro Ziliani 

Thanks for the answer.

I start with connman because in meta-qt5 there the recipe for it.

I keep on with connman.


MZ


Il 17/05/2018 15:00, Mirza Krak ha scritto:

On 17 May 2018 at 14:18, Mauro Ziliani  wrote:

Hi all.

Which the betst choice to perform the network configuration in Yocto Krogoth
from a qt5 application?

The configuration should be made without external script, using dbus.

Well you probably need to use a network manager that you can control
trough D-Bus. NetworkManager, ConnMan, systemd-networkd etc.

If you are using ConnMan you can use this:
https://git.merproject.org/mer-core/libconnman-qt

There might exist similar libraries for other network managers but I
am not aware of any.



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

[yocto] Using yocto as a build system

2018-05-17 Thread mamta0925 
Hi,

Apologies if these are basic questions but thought this will be the best place 
to find answers to the point

So our requirement is to build open source packages in Linux, windows and Mac 
on a build system. Currently we have an internal build system which is quite 
cumbersome to manage. Hence we are looking for outside options

Given our situation, is Yocto our best solution? Does it even provide for 
building windows and Mac open source packages? 

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

Re: [yocto] Enabling the recipe from menuconfig

2018-05-17 Thread chandrasekhar 
you want to see in kernel menuconfig??

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ugesh Reddy
Sent: Friday, May 18, 2018 7:52 AM
To: 'Yocto-mailing-list'; chandrasekhar
Subject: Re: [yocto] Enabling the recipe from menuconfig

 

Hi,

Thanks for the response,

 

 This will add the recipe as a part of image but I want to build and add the 
recipe when it has been selected from the menuconfig.

How to make visible the recipe in menuconfig?

On Thursday, 17 May, 2018, 9:32:15 AM IST, chandrasekhar 
 wrote: 

 

 

Hi 

You can use 

IMAGE_INSTALL += "Package Name/Recipes name"

 

Regards,

Chandrasekhar

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ugesh Reddy
Sent: Wednesday, May 16, 2018 9:57 PM
To: Yocto-mailing-list
Subject: [yocto] Enabling the recipe from menuconfig

 

Hello Team,

 

 I have a list of recipes in my custom layer. The recipes in this layer shall 
be enabled/selected through the menuconfig, once it is enabled then it shall be 
the part of image. is it possible to achieve it ? do we have any references? 

 

Regards,

Ugesh

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

Re: [yocto] [OE-core] [RFT] GCC 8.1

2018-05-17 Thread Khem Raj 
On Thu, May 17, 2018 at 3:46 AM, Martin Jansa  wrote:
> On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote:
>> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused
>> > > this, it build OK with sumo since the -std=gnu99 addition.
>> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated
>> > > before the last format character [-Werror=format-truncation=]
>> > >   "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$",
>> > >   ^~~
>> > >
>> >
>> > something new, I will look into reproducing this.
>
> The fix from you worked for me, thanks!

There is a followup here which now doesnt need local patch

http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=0924a69244892097f60adbf6c7f576375bea7870

> Just FYI if someone needs similar fix, backporting this:
> https://patchwork.kernel.org/patch/9170055/
>
> fixed the issue for me, now I have successful kernel build.
>
> The failing code was always in put_user calls, e.g. kernel/exit.s was showing:
> @ 1581 "kernel-source/kernel/exit.c" 1
> .ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; 
> .ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif
> .ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; 
> .ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif
> .ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; 
> .ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif
> bl  __put_user_4
> @ 0 "" 2
>
> with the error triggered on the middle line.
> /tmp/ccHq8ugv.s: Assembler messages:
> /tmp/ccHq8ugv.s:1179: Error: .err encountered
> /tmp/ccHq8ugv.s:1331: Error: .err encountered
> /tmp/ccHq8ugv.s:4617: Error: .err encountered
> /tmp/ccHq8ugv.s:6222: Error: .err encountered
> /tmp/ccHq8ugv.s:8705: Error: .err encountered
> /tmp/ccHq8ugv.s:14486: Error: .err encountered
> /tmp/ccHq8ugv.s:14646: Error: .err encountered
> /tmp/ccHq8ugv.s:14806: Error: .err encountered
> /tmp/ccHq8ugv.s:14966: Error: .err encountered
> /tmp/ccHq8ugv.s:15126: Error: .err encountered
> /tmp/ccHq8ugv.s:15286: Error: .err encountered
>
> That leaves only few issues in our internal components and strange failure 
> with perf which fails to include various header files:

perf is building file for qemux86 on o-core
I wonder if this is an issue related to your
kernel version.


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

[yocto] [meta-openstack][PATCH] python-requests: remove PREFERRED_VERSION limit

2018-05-17 Thread mingli.yu 
From: Mingli Yu 

* Previously, add PREFERRED_VERSION for python-requests
  as we want to use version >=2.10.0 and the full commit
  message as below:

  commit 185eccef8964632f5b255265a0a8e59fe5858397
  Author: Mark Asselstine 
  Date:   Fri Jan 20 16:59:31 2017 -0500

python-requests: use version from meta-openembedded

We want to use a version >=2.10.0 as required by python-keystoneauth1
so set a PREF so we don't get the older version found in
meta-virtualization and used by docker.

Signed-off-by: Mark Asselstine 
Signed-off-by: Bruce Ashfield 

* Now meta-oe upreved python-requests to 2.18.4, remove
  PREFERRED_VERSION limit to avoid bitbake messages like:

  "NOTE: preferred version 2.13.0 of python-requests not available"

Signed-off-by: Mingli Yu 
---
 meta-openstack/conf/layer.conf | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta-openstack/conf/layer.conf b/meta-openstack/conf/layer.conf
index 55df509..c376d58 100644
--- a/meta-openstack/conf/layer.conf
+++ b/meta-openstack/conf/layer.conf
@@ -31,7 +31,6 @@ PREFERRED_VERSION_python-futures = "3.0.3%"
 PREFERRED_VERSION_python-django = "1.8.6"
 PREFERRED_VERSION_python-netaddr = "0.7.19"
 PREFERRED_VERSION_python-sqlalchemy = "1.0.16"
-PREFERRED_VERSION_python-requests = "2.13.0"
 PREFERRED_VERSION_python-eventlet = "0.20.0"
 PREFERRED_VERSION_python-warlock = "1.2.0"
 PREFERRED_VERSION_python-jsonschema = "2.6.0"
-- 
2.7.4

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

Re: [yocto] Enabling the recipe from menuconfig

2018-05-17 Thread chandrasekhar 
I think you can use Toaster for that which has a web interface you can select 
packages/receipes

 

Regards,

Chandrasekhar

 

From: Ugesh Reddy [mailto:kumar.ugesh...@yahoo.com] 
Sent: Friday, May 18, 2018 11:15 AM
To: chandrasek...@evolute.in; 'Yocto-mailing-list'
Subject: RE: [yocto] Enabling the recipe from menuconfig

 

The similar kind is required for my custom layer. So that I could enable the 
receipt from the menu config

Sent from Yahoo   Mail on 
Android

 

On Fri, 18 May 2018 at 9:44 a.m., chandrasekhar

 wrote:

you want to see in kernel menuconfig??

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ugesh Reddy
Sent: Friday, May 18, 2018 7:52 AM
To: 'Yocto-mailing-list'; chandrasekhar
Subject: Re: [yocto] Enabling the recipe from menuconfig

 

Hi,

Thanks for the response,

 

 This will add the recipe as a part of image but I want to build and add the 
recipe when it has been selected from the menuconfig.

How to make visible the recipe in menuconfig?

On Thursday, 17 May, 2018, 9:32:15 AM IST, chandrasekhar 
 wrote: 

 

 

Hi 

You can use 

IMAGE_INSTALL += "Package Name/Recipes name"

 

Regards,

Chandrasekhar

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ugesh Reddy
Sent: Wednesday, May 16, 2018 9:57 PM
To: Yocto-mailing-list
Subject: [yocto] Enabling the recipe from menuconfig

 

Hello Team,

 

 I have a list of recipes in my custom layer. The recipes in this layer shall 
be enabled/selected through the menuconfig, once it is enabled then it shall be 
the part of image. is it possible to achieve it ? do we have any references? 

 

Regards,

Ugesh

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

[yocto] apt-get error

2018-05-17 Thread Rahul jangra 
-- Forwarded message --
From: Rahul jangra 
Date: Thu, 17 May 2018 10:29:16 +0530
Subject: Re: [yocto] apt-get error
To: Anuj Mittal 

when I am creating core-image-minimal it easy to build up
but when I am trying to create core-image-full-cmdline he is getting an error

ore-image-full-cmdline-1.0-r0 do_rootfs: Unable to install packages.
Command 
'/home/debianstretch/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
 install --force-yes --allow-unauthenticated dpkg base-passwd
hello-mender packagegroup-core-ssh-openssh psplash-raspberrypi
run-postinsts shadow packagegroup-core-boot kernel-devicetree
kernel-image-4.14.39 mender packagegroup-core-full-cmdline apt'
returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 packagegroup-core-full-cmdline : Depends:
packagegroup-core-full-cmdline-initscripts but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.

ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/debianstretch/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/temp/log.do_rootfs.105216
ERROR: Task 
(/home/debianstretch/poky-rocko/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs)
failed with exit code '1'





On 5/17/18, Rahul jangra  wrote:
> I am working on mender yocto project of raspberry pi
> and I am sharing my details
> my local.conf file setting
> # Local configuration for meta-RPI images
> # Yocto Project 2.4 Poky distribution [rocko] branch
> # This is a sysvinit system
>
> LICENSE_FLAGS_WHITELIST = "commercial"
>
> DISTRO_FEATURES = "ext2 pam opengl usbhost ${DISTRO_FEATURES_LIBC}"
>
> DISTRO_FEATURES_BACKFILL_CONSIDERED += "pulseaudio"
>
> PREFERRED_PROVIDER_jpeg = "libjpeg-turbo"
> PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"
>
> PREFERRED_PROVIDER_udev = "eudev"
> #VIRTUAL-RUNTIME_init_manager = "sysvinit"
>
> MACHINE_FEATURES_remove = "apm"
>
> IMAGE_FSTYPES = "tar.xz"
>
> # override the meta-raspberrypi default 4.9 kernel
> PREFERRED_VERSION_linux-raspberrypi = "4.14.%"
>
> # Choose the board you are building for
> #MACHINE="raspberrypi"
> #MACHINE="raspberrypi0"
> #MACHINE="raspberrypi0-wifi"
> #MACHINE="raspberrypi2"
> #MACHINE = "raspberrypi3"
> #MACHINE="raspberrypi-cm"
> #MACHINE="raspberrypi-cm3"
>
> # Choices are Image or zImage if NOT using u-boot (no u-boot is the
> default)
> # Choices are uImage or zImage if using u-boot, though if you choose zImage
> # with u-boot you will also have to change the boot script boot command
> #KERNEL_IMAGETYPE = "zImage"
>
> ENABLE_UART="1"
>
> DL_DIR = "${HOME}/oe-sources"
>
> #SSTATE_DIR = "/oe4/rpi/sstate-cache"
>
> #TMPDIR = "/oe4/rpi/tmp-rocko"
>
> DISTRO = "poky"
>
> #PACKAGE_CLASSES = "package_ipk"
> PACKAGE_CLASSES = "package_deb"
>
> # i686 or x86_64
> SDKMACHINE = "x86_64"
>
> EXTRA_IMAGE_FEATURES = "debug-tweaks"
> INHERIT += "extrausers"
> EXTRA_USERS_PARAMS = "usermod -P nsspl@123 root; "
>
> USER_CLASSES = "image-mklibs image-prelink"
>
> PATCHRESOLVE = "noop"
>
> RM_OLD_IMAGE = "1"
>
> INHERIT += "rm_work"
>
> ONF_VERSION = "1"
>
> # The name of the disk image and Artifact that will be built.
> # This is what the device will report that it is running, and
> different updates must have different names
> # because Mender will skip installation of an Artifact if it is
> already installed.
> MENDER_ARTIFACT_NAME = "release-1"
>
> INHERIT += "mender-full"
>
> # A MACHINE integrated with Mender.
> # raspberrypi3, beaglebone, and vexpress-qemu are reference devices
> MACHINE = "raspberrypi3"
>
> # For Raspberry Pi, uncomment the following block:
> RPI_USE_U_BOOT = "1"
> #MENDER_PARTITION_ALIGNMENT_KB = "4096"
> #MENDER_BOOT_PART_SIZE_MB = "40"
> MENDER_PARTITION_ALIGNMENT_KB = "8192"
> MENDER_BOOT_PART_SIZE_MB = "80"
> MENDER_DATA_PART_SIZE_MB = "128"
> MENDER_STORAGE_TOTAL_SIZE_MB = "5000"
> do_image_sdimg[depends] += " bcm2835-bootfiles:do_populate_sysroot"
> IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
> IMAGE_FSTYPES_remove += " rpi-sdimg"
>
> # Lines below not needed for Yocto Rocko (2.4) or newer.
> # IMAGE_BOOT_FILES_append = " boot.scr u-boot.bin;${SDIMG_KERNELIMAGE}"
> KERNEL_IMAGETYPE = "uImage"
>
> # The version of Mender to build. This needs to match an existing
> recipe in the meta-mender repository.
> #
> # Given your Yocto Project version, see which versions of Mender you
> can currently build here:
> #
> https://docs.mender.io/architecture/compatibility#mender-client-and-yocto-

Re: [yocto] Enabling the recipe from menuconfig

2018-05-17 Thread Andrea Galbusera 
On Fri, May 18, 2018 at 6:14 AM, chandrasekhar  wrote:
> you want to see in kernel menuconfig??
>
>
>
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Ugesh Reddy
> Sent: Friday, May 18, 2018 7:52 AM
> To: 'Yocto-mailing-list'; chandrasekhar
> Subject: Re: [yocto] Enabling the recipe from menuconfig
>
>
>
> Hi,
>
> Thanks for the response,
>
>
>
>  This will add the recipe as a part of image but I want to build and add the
> recipe when it has been selected from the menuconfig.
>
> How to make visible the recipe in menuconfig?

Unlike other distribution build systems, Yocto/OE don't provide any
menuconfig based configuration interface for selecting which package
to include in images you build. There is indeed support for accessing
menuconfig interfaces provided by specific recipes like the linux
kernel. If you need a high level recipe selection tool, your best bet
is probably to look at Toaster.

>
> On Thursday, 17 May, 2018, 9:32:15 AM IST, chandrasekhar
>  wrote:
>
>
>
>
>
> Hi
>
> You can use
>
> IMAGE_INSTALL += "Package Name/Recipes name"
>
>
>
> Regards,
>
> Chandrasekhar
>
>
>
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Ugesh Reddy
> Sent: Wednesday, May 16, 2018 9:57 PM
> To: Yocto-mailing-list
> Subject: [yocto] Enabling the recipe from menuconfig
>
>
>
> Hello Team,
>
>
>
>  I have a list of recipes in my custom layer. The recipes in this layer
> shall be enabled/selected through the menuconfig, once it is enabled then it
> shall be the part of image. is it possible to achieve it ? do we have any
> references?
>
>
>
> Regards,
>
> Ugesh
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto