[yocto] FriendlyArm Mini6410 ?

Hello Everyone, I want to use Yocto for my FriendlyArm Mini6410, Where should I begin to start ? Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Release Candidate Build for yocto-2.4_M1.rc1 now available.

A release candidate build for yocto-2.4_M1.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.4_M1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 86c55b1296a1c0b1fab6a3fd339bed0aafc92c07 meta-qt4 :

Re: [yocto] [meta-selinux] [PATCH] audit: 2.7.1 -> 2.7.6

Ping Zheng Ruoqin Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) ADDR.: No.6 Wenzhu Road, Software Avenue, Nanjing, 210012, China MAIL : zhengrq.f...@cn.fujistu.com -Original Message- From: Zheng, Ruoqin/郑 若钦 Sent: Thursday, May 25, 2017 6:39 PM To: yocto@yoctoproject.org

Re: [yocto] devshell not working for Qt or Boundary Devices based yocto

On 2017-06-15 01:58, Jimi Damon wrote: Hi , I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) . What are you expecting to happen? 'devshell' is just that - a shell

[yocto] Is linux-yocto-rt kernel compatible with x32 tune?

I've been fighting with this off and on for a week. If I build core-image-minimal for a generic86-64 machine, I can get it to use the x32 ABI, or I can switch to the linux-yocto-rt 4.8 kernel, but I can't do both. If I do both, it builds with no complaint other than a lot of bit size errors in

[yocto] devshell not working for Qt or Boundary Devices based yocto

Hi , I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) . I'm invoking it with bitbake -c devshell core-image-minimal bitbake --version = 1.32.0 I'm getting my

[yocto] QA cycle report for 2.1.3 rc1

Hello All, Here is the report for the 2.1.3 rc1 full point release test cycle. Full Report : https://wiki.yoctoproject.org/wiki/WW24_-_2017-14-06_-_Full_Pass_2.1.3_rc1 Summary The QA cycle for release 2.1.3 rc1 is complete, there were 4 new issues related to the

Re: [yocto] locale error at do_rootfs step

On 6/14/17 1:29 AM, Dvorkin Dmitry wrote: > I'm using the newest master branch of poky, with DNF. Host PC locale is > non-EN. > > setting host PC LANG and LC_* to en_US doesn't help > > Got a strange error: > > > NOTE: Executing RunQueue Tasks > ERROR: MyIMG-1.0-r1 do_rootfs: [log_check]

Re: [yocto] do_rootfs failed with message about host system(?) locale

On 6/14/17 3:46 AM, Dvorkin Dmitry wrote: > ERROR: MyIMG-1.0-r1 do_rootfs: [log_check] MyIMG: found 2 error messages > in the logfile: > [log_check] Failed to set locale, defaulting to C > [log_check] Failed to set locale, defaulting to C Do you have locale setup correctly on your build host ? >

[yocto] How to package the signed kernel modules into the filesystem ?

Hi, I am working with kernel 3.10.17 and poky daisy. The kernel was patched to support certificates list & trusted keyring. I managed to build the kernel both with an own keypair (signature done manually post-build) and with the CONFIG_MODULE_SIG_ALL option enabled. In the second case, I

Re: [yocto] [PATCH] documentation: updates to static library support in SDK

On Wed, Jun 14, 2017 at 5:12 AM, Maxin B. John wrote: > For development purposes, static libraries need to be > present only in the SDK. We do not need those static > libraries in the image for most scenarios. So, replace > IMAGE_INSTALL with TOOLCHAIN_TARGET_TASK in the

Re: [yocto] useradd and one sysroot per recipe in pyro

On Wed, 2017-06-14 at 18:12 +0200, Laurent Gauthier wrote: > Hi Christian, > > In pyro the creation of users and group (using the useradd class) is > done during the package pre-installation. > > So my best guess is that you could move the owner/group change in the > package post-installation as

Re: [yocto] useradd and one sysroot per recipe in pyro

Hi Christian, In pyro the creation of users and group (using the useradd class) is done during the package pre-installation. So my best guess is that you could move the owner/group change in the package post-installation as follows: do_install () { (…) install -d

Re: [yocto] useradd and one sysroot per recipe in pyro

Hi Maxin, > Here, could you try to build again with an additional DEPENDENCY on shadow- > native: > ie: instead of > >DEPENDS = "puck-base" > DEPENDS = "puck-base shadow-native" > > To be sure, please cleansstate the puck-base and test before build. Thanks! I tried as you suggested (cleansstate

[yocto] useradd and one sysroot per recipe in pyro

Any ideas how to use "useradd" bbclass with pyro? If I move useradd to my recipe my-appl.bb, it works. But there are more recipes depending on the added user, so I want to add this user in a base-recipe and just depend on it using (DEPENDS/RDEPENDS). Regards Christian Von: Andersen, Christian

Re: [yocto] Issue building core-image-minimal

Hi Charmi, I am not entirely sure of what is going on in your case, but one possible issue that could occur is that you are behind a network proxy inside a corporate network. When using the GIT protocol (as in the case you are showing) you might need to configure git to use your proxy properly.

Re: [yocto] useradd and one sysroot per recipe in pyro

Hi Andersen, On Tue, Jun 13, 2017 at 04:10:10PM +, Andersen, Christian wrote: > >Hello, >currently I am trying the newest Yocto release (pyro). It seems I have a >problem >with useradd and the new concept of one sysroot per recipe. > >I have a base recipe (let’s call it my-base.bb) which

Re: [linux-yocto] [linux-yocto-3.14] [PATCH] security/keys: fixed crash in keyring_destroy

merged. Bruce On 06/14/2017 01:09 PM, Daniel Dragomir wrote: From: Charlie Paul *For 3.14 standard/(preempt-rt)/axxia/base branches. When the ltp add_key01 was run the kernel was crashing, the list_del initializes the next pointer to LIST_POISON1. When subsequent

[yocto] Issue building core-image-minimal

Hi, I am new to Yocto Project and I am taking training for Yocto.I have a basic understanding about Yocto. I was going through the quick start guide and followed all the steps to build custom linux for core-image-minimal. When I give the commands: bitbake core-image-minimal I get the following

[yocto] [PATCH] documentation: updates to static library support in SDK

For development purposes, static libraries need to be present only in the SDK. We do not need those static libraries in the image for most scenarios. So, replace IMAGE_INSTALL with TOOLCHAIN_TARGET_TASK in the documentation. Suggested-by: Anders Darander Signed-off-by:

Re: [yocto] is there a guide to making a recipe for bitbake with the morty/pyro branch

Hi James On Wednesday, 14 June 2017 12:43:24 PM CEST blackthirt33n . wrote: > is there a guide to making a recipe for bitbake with the more recent > branches. > I have found a guide but those are dated 2015 and there descriptions > are now dated. The relevant section of the manual is here:

[linux-yocto] [linux-yocto-3.14] [PATCH] security/keys: fixed crash in keyring_destroy

From: Charlie Paul *For 3.14 standard/(preempt-rt)/axxia/base branches. When the ltp add_key01 was run the kernel was crashing, the list_del initializes the next pointer to LIST_POISON1. When subsequent keyring destroy events happened, the system would check for NULL

[yocto] do_rootfs failed with message about host system(?) locale

ERROR: MyIMG-1.0-r1 do_rootfs: [log_check] MyIMG: found 2 error messages in the logfile: [log_check] Failed to set locale, defaulting to C [log_check] Failed to set locale, defaulting to C ERROR: MyIMG-1.0-r1 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in:

Re: [yocto] Image lacks libraries needed by SDK

Hi Anders, On Wed, Jun 14, 2017 at 11:20:57AM +0200, Anders Darander wrote: > * Maxin B. John [170614 10:24]: > > > Hi Paul, > > > On Tue, Jun 13, 2017 at 04:24:38PM -0700, Paul D. DeRocco wrote: > > > In order to try out the much more recent compiler in the Yocto SDK

[yocto] is there a guide to making a recipe for bitbake with the morty/pyro branch

is there a guide to making a recipe for bitbake with the more recent branches. I have found a guide but those are dated 2015 and there descriptions are now dated. James -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] Image lacks libraries needed by SDK

* Maxin B. John [170614 10:24]: > Hi Paul, > On Tue, Jun 13, 2017 at 04:24:38PM -0700, Paul D. DeRocco wrote: > > In order to try out the much more recent compiler in the Yocto SDK (and to > > prepare for converting to a different architecture in the future), I built > > a

Re: [yocto] Image lacks libraries needed by SDK

Hi, On Wed, Jun 14, 2017 at 01:34:40AM -0700, Paul D. DeRocco wrote: > > From: Maxin B. John [mailto:maxin.j...@intel.com] > > > > Had a similar experience with respect to the availability of > > static libraries in the SDK. > > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5347 > >

Re: [yocto] swupate.bblcass dependencies not triggering rebuild

Hi Andreas, On 13/06/2017 14:18, Andreas Fenkart wrote: > Hi list, > > I want to create a swupdate file, which is a cpio file with rootfs and > some metadata to control software update. My problem is, that it is not > rebuilt everytime the rootfs changes. I checked in the cooker log. > > NOTE:

Re: [yocto] Image lacks libraries needed by SDK

> From: Maxin B. John [mailto:maxin.j...@intel.com] > > Had a similar experience with respect to the availability of > static libraries in the SDK. > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5347 > > One way to fix this will be to include required static > libraries in the image >

Re: [yocto] Image lacks libraries needed by SDK

Hi Paul, On Tue, Jun 13, 2017 at 04:24:38PM -0700, Paul D. DeRocco wrote: > I have a working system image for my 32-bit Atom-based hardware, based on > Morty. My application is a C++ program that runs as a systemd service. > I've always built the application outside Yocto, using the Eclipse CDT

[yocto] [bitbake] How to figure out that a recipe is executed during the populatye_sdk task ?

I wrote a recipe for our ARM board linux that compiles a bunch of sources and produces some binary executables for the target board. Everything is done properly with do_compile, do_install etc. The binary executables that need to be deployed on the target board are installed in do_install