[yocto] How to set password policy using libpam in yocto

Hi, I want to create run time users in my target and the password for that should have maximum of 12 letters (which include both capital and small) and minimum of 8 letter. How can i modify "libpam" recipe to set this configuration . where to add libpam recipe. I found in one blog that i

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

Hi, On 11 January 2016 at 06:21, wrote: > Hello, > > You are receiving this email because you are the maintainer > of *gpgme* recipe and this is to let you know that the automatic attempt > to upgrade the recipe to *1.6.0* has Succeeded. > First, thanks for the

Re: [yocto] How to build jffs2 rootfs image in freescale community build

hi , On similar lines i want to rebuild my linux dtb file as i have made some changes in my dts file . How can i force it to regenerate the same ? For example , I use the command bitbake -c compile -f linux-ls1 to regenerate the uImage . Is there is similar command for the linux-dtb generation

Re: [yocto] How to build jffs2 rootfs image in freescale community build

Great . That helped . Thanks for a quick reply. Can you point me to any documentation that would help answer these kind of questions for me ? Thanks and Regards, Sarayu K S Tech Lead Zaikenn Technologies On Wed, Jan 13, 2016 at 11:22 PM, Khem Raj wrote: > you need to run

Re: [yocto] [Yocto][Generic] Add a local binary file into a target Distro

On 13 January 2016 at 20:16, Karim ATIKI wrote: > But, although I've been able to add my own layer to include a project from > github, I was just wondering how we could simply and easily add a local > file / binary to a target distro ? (FYI: raspberrypi2) without

[yocto] [Yocto][Generic] Add a local binary file into a target Distro

Hi all, Please be indulgent with my noob question. I spent a lot of time with setting up Yocto on different target boards. It's just amazing. But, although I've been able to add my own layer to include a project from github, I was just wondering how we could simply and easily add a local

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

On 13 January 2016 at 20:03, Paul Eggleton wrote: > I'd question the value of -a as well; the tool is supposed to be smart > enough > to show you the things that matter and hide everything else by default. If > it's not doing that effectively then we should fix it.

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

On Wed, 13 Jan 2016 11:08:40 Aníbal Limón wrote: > On 01/13/2016 07:42 AM, Jussi Kukkonen wrote: > > On 11 January 2016 at 06:21, wrote: > >> You are receiving this email because you are the maintainer > >> of *gpgme* recipe and this is to let you know that the

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

On 13 January 2016 at 20:27, Anibal Limon wrote: > If we don't use -a option the PKGR changes are not shown. I don't know > if buildhistory-diff needs another improvements :D. > Yeah, my request was general, not specific to AUH. That's probably because the AUH doesn't

[yocto] findutils_4.4.2.bb is having rev-6 and findutils_4.4.2.bbappend has having rev-6.5 , which findutils will it include in image recipe

hi, I want to include findutility recipe in the rootfs. there in findutils_4.4.2.bb recipe in poky-1.7/meta layer and PR = "r6" there is findutils_4.4.2.bbappend in meta-selinux layer it has PR .= ".5" when i build findutils In *tmp/work/core###/findutils*/// there

[yocto] Package naming "exceptions" in Yocto

Hi, I have a small question about "exceptional" names of packages in yocto/OE. Kernel package is being one example with the name "linux-yocto" vs. traditional "linux_kernel". Are there more such yocto-specific packages (of course excluding FW and other bsp-related packages)? A look over the

[yocto] [[PATCH][AUH] 2/2] steps.py: Adds {pack, unpack}_original_workdir.

The original workdir directory is needed for make diff's for example when license change [1], in order to avoid deletion of original workdir when recipe is upgraded. Signed-off-by: Aníbal Limón [1]

[yocto] [meta-raspberrypi][PATCH] rpi-gpio: Upgrade to 0.6.1 and fix build with clang

Signed-off-by: Khem Raj --- .../rpi-gpio/0001-Remove-nested-functions.patch| 294 + .../{rpi-gpio_0.5.11.bb => rpi-gpio_0.6.1.bb} | 6 +- 2 files changed, 298 insertions(+), 2 deletions(-) create mode 100644

[yocto] [matchbox-keyboard][PATCH] config-parser: Use matching printf format

XML_GetCurrentLineNumber() returns unsigned long as clang is telling us here src/config-parser.c:603:6: warning: format specifies type 'int' but the argument has type 'XML_Size' (aka 'unsigned long') [-Wformat] XML_GetCurrentLineNumber(p), ^~~

[yocto] [[PATCH][AUH] 1/2] buildhistory.py: Add the ability for generate full and simple output.

Now buildhistroy generate two diff files, - buildhistory-diff.txt: Simple diff generated without -a option. - buildhistory-diff-full.txt: Full diff generated contains all the packages including -dbg and -dev. Signed-off-by: Aníbal Limón

[yocto] [meta-raspberrypi][PATCH] eglinfo-x11, eglinfo-fb: Add EGLINFO_DEVICE via bbappends

Signed-off-by: Khem Raj --- recipes-graphics/eglinfo/eglinfo-fb_%.bbappend | 1 + recipes-graphics/eglinfo/eglinfo-x11_%.bbappend | 1 + 2 files changed, 2 insertions(+) create mode 100644 recipes-graphics/eglinfo/eglinfo-fb_%.bbappend create mode 100644

Re: [yocto] How to set password policy using libpam in yocto

On 01/13/2016 06:20 PM, Vivek Per wrote: Hi, I want to create run time users in my target and the password for that should have maximum of 12 letters (which include both capital and small) and minimum of 8 letter. How can i modify "libpam" recipe to set this configuration . where to add

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

Hi Jussi, Thanks for the feedback, comments below... Cheers, alimon On 01/13/2016 07:42 AM, Jussi Kukkonen wrote: > Hi, > > On 11 January 2016 at 06:21, wrote: > >> Hello, >> >> You are receiving this email because you are the maintainer >> of *gpgme*

[yocto] Upstream U-Boot fetch failure (Jethro)

Hi all, When fetching from upstream U-Boot, I am encountering an initial fetch failure that "breaks" the current build. After this initial failure, successive executions of the recipe allows it to continue. The minimal recipe for me to reproduce this is a simple two liner. u-boot_2016.01.bb:

Re: [yocto] [meta-java] openjdk-8 fail to build

Hi again, looking to the above error on Makefile, seems there is still something wrong with autotools cat /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile # This Makefile was generated by configure Tue

Re: [yocto] How to build jffs2 rootfs image in freescale community build

you need to run -c deploy task for that On Wed, Jan 13, 2016 at 9:48 AM, Sarayu Krishna Sivanandam wrote: > hi , > > I do see the the linux-dtb.inc included in the linux-ls1 recipe but when i > build the code using > > bitbake -c compile -f linux-ls1 it doesnot re-generate

Re: [yocto] How to build jffs2 rootfs image in freescale community build

> On Jan 13, 2016, at 4:03 AM, Sarayu Krishna Sivanandam > wrote: > > hi , > > On similar lines i want to rebuild my linux dtb file as i have made some > changes in my dts file . How can i force it to regenerate the same ? > > For example , I use the command bitbake -c

Re: [yocto] How to build jffs2 rootfs image in freescale community build

hi , I do see the the linux-dtb.inc included in the linux-ls1 recipe but when i build the code using bitbake -c compile -f linux-ls1 it doesnot re-generate the dtb file in the deploy/images/ls1021atwr folder . Also when i try to rebuild the images like core-image-minimal or core-image base it