Re: [yocto] populate_sdk with my image

t general behavior is the same. --Mark > Il 21/11/19 17:40, Mark Hatle ha scritto: >> populate_sdk uses the same configuration as the regular image, as well as >> adding >> "dev-pkgs dbg-pkgs src-pkgs" and optionally doc-pkgs. >> >> See: >> http:/

Re: [yocto] populate_sdk with my image

populate_sdk uses the same configuration as the regular image, as well as adding "dev-pkgs dbg-pkgs src-pkgs" and optionally doc-pkgs. See: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/populate_sdk_base.bbclass Lines 3-11, and 22. If dev-pkgs/src-pkgs isn't inclyding your

Re: [yocto] busybox + SELinux (warrior) - reboot issue

I've been trying to find time to look into it, but I've not had any so far. I'd suggest trying it on more full Linux system first to see if that resolves the issue. If it does, then it's simply a configuration and you can use the audit messages to help figure it out.. but the fact it's

Re: [yocto] :how to solve the basehash value changed from 'xxx' to 'aaaa' ?

You are changing the value of something in there dynamically. Most likely you've done something like embed the current date and time. If you do something like that, you need to evaluate it -once- during parse time and not again. This will fix the hash value at parse time and not change it

Re: [yocto] No Package Provides /bin/awk

Bitbake inspects the binaries and looks at the #! line. You need to change the line itself (via a patch) to /usr/bin/awk, and then it will pick up the dependency automatically on a rebuild. --Mark On 11/13/19 12:14 PM, Wayne Li wrote: > On further inspection of the older image my coworker made,

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

When cloning a repository using the builtin fetcher that is git based, the default protocol is 'git'. If you want to use an alternative protocol, such as http or ssh, you must specify the protocol to use. In your example below, you have specified http: SRC_URI =

Re: [yocto] [OE-core] [prelink-cross] Bug 13529 add SPDX identifier

: > > > On Mon, Oct 21, 2019 at 4:35 PM Mark Hatle <mailto:mark.ha...@kernel.crashing.org>> wrote: > > On 10/21/19 4:43 AM, Yann CARDAILLAC wrote: > > Hi Mark Hatle, Jakub Jelinek, > > Jakub is no longer supporting this code, but he may have valua

[yocto] toaster - in build watching mode

I'm using toaster in a build watching mode and I'm getting errors to the console log such as: File: '/home/jenkins/workspace/OEBuild/build-32/oe-core/meta/classes/toaster.bbclass', lineno: 130, function: toaster_package_dumpdata 0126:lpkgdata = {} 0127:datadir =

Re: [yocto] Useradd: crypted passwords longer than 8 characters

Crypt the password yourself and pass it in to the adduser command. --Mark On 10/21/19 10:25 AM, Lukasz Zemla wrote: > What is the best way in Yocto (warrior) to add crypted password to > /etc/shadow during buildtime? > > Using useradd.bbclass in a standard way we may add only passwords <= 8 >

Re: [yocto] [OE-core] [prelink-cross] Bug 13529 add SPDX identifier

On 10/21/19 4:43 AM, Yann CARDAILLAC wrote: > Hi Mark Hatle, Jakub Jelinek, Jakub is no longer supporting this code, but he may have valuable insights into licensing. > I'm currently beginning the work on bug 13529: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13529 >

Re: [yocto] [layerindex-web] Enabled zeus, not working...

On 10/14/19 5:08 PM, Paul Eggleton wrote: > Hi Mark > > On Tuesday, 15 October 2019 10:21:29 AM NZDT Mark Hatle wrote: >> I added the zeus branch on the layers.openembedded.org today and it's not >> showing up and being indexed. Any idea why? > > The bitbake branch

[yocto] [layerindex-web] Enabled zeus, not working...

I added the zeus branch on the layers.openembedded.org today and it's not showing up and being indexed. Any idea why? On my own personal layer index I did it and it worked fine. So it may be something related to the configuration. Below are the errors from the update log: Oct. 14, 2019, 7:13

Re: [yocto] No SELinux security context (/etc/crontab)

There SE Linux policy included in meta-selinux is just a starting point. It's expected that you will have to update/customize it. With that said, these types of issues, we will accept patches for them. --Mark On 10/10/19 5:06 AM, Oriya, Raxesh wrote: > Hi, > >   > > I have enabled SELinux in

[yocto] [layerindex-web] [PATCH 3/3] RFC: editlayer: Be more specific on the searches

. Signed-off-by: Mark Hatle --- layerindex/tools/import_layer.py | 8 layerindex/tools/import_wiki_layers.py | 13 ++--- templates/layerindex/editlayer.html| 8 3 files changed, 18 insertions(+), 11 deletions(-) diff --git a/layerindex/tools/import_layer.py b

[yocto] [layerindex-web] [PATCH 2/3] update.py: Allow bitbake to live in a subdirectory of a repository

this is a reasonable compromise, since in a combined repository bitbake and openembedded-core component should already match. Signed-off-by: Mark Hatle --- docker/settings.py | 3 +++ layerindex/bulkchange.py | 8 +++- layerindex/layerconfparse.py | 8 +++- layerindex/update.py | 14

[yocto] [layerindex-web] [PATCH 1/3] layerindex/urls.py: Allow branches with a '.' in the name

Without this change the system will fail parsing various URL components Signed-off-by: Mark Hatle --- layerindex/urls.py | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/layerindex/urls.py b/layerindex/urls.py index 7f4e545..89e70a2 100644 --- a/layerindex

[yocto] [layerindex-web] [PATCH 0/3] Some misc changes/fixes..

vcs_web_url submissions... so I tried to make it better.. but I'm not sure it's right. Mark Hatle (3): layerindex/urls.py: Allow branches with a '.' in the name update.py: Allow bitbake to live in a subdirectory of a repository editlayer: Be more specific on the searches docker/settings.py

Re: [yocto] [meta-openssl102-fips][PATCH 3/3] nss: conditionally enable fips

The original goal of this work was to enable a FIPS-140-2 OpenSSL module. Why is NSS part of this? Is something inside of the OpenSSL patches requesting NSS support, or is this a different -- but related request? --Mark On 10/12/19 3:17 AM, Hongxu Jia wrote: > Add export NSS_FORCE_FIPS=1 to

Re: [yocto] [meta-openssl102-fips][PATCH] README.build/image.inc: add missing openssl-fips to image

merged. --Mark On 10/9/19 3:28 AM, Hongxu Jia wrote: > For Yocto and WRLinux, openssl fips works only if installing > package openssl-fips > > Signed-off-by: Hongxu Jia > --- > README.build | 1 + > templates/feature/openssl-fips/image.inc | 1 + > 2 files changed,

[yocto] [layerindex-web] Having problems instantiating a docker image

I've setup the layerindex in the past (without docker).. but I'm attempting to follow the current instructions w/o much success. I'm trying to use: ./dockersetup.py -m 8080:80 --no-https It asks me for my email address and then builds the docker images... then I get a failure connecting to

Re: [yocto] meta-selinux warrior support

I thought this issue was already fixed: http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?h=warrior=bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0 This patch is what specifically adds the enabled/disabled that the system is saying (in the logs quoted below) is invalid. Can you try

Re: [yocto] Xilinx/meta-jupyter layer

On 9/27/19 3:12 PM, Chandana Kalluri wrote: > Hello all, > > https://github.com/Xilinx/meta-jupyter is a meta-jupyter layer containing > recipes for jupyter notebook. The initial recipes are based of Dmitry > Kargin's meta-jupyter layer >

Re: [yocto] Transfer meta-data between recipes

On 9/26/19 8:59 AM, Westermann, Oliver wrote: > Hey, > >   > > I’m trying to implement a bootloader-signing mechanism within yocto for > extended > secure-boot support. The bootloader and it’s recipes are provided by NXP (in > this case it’s the imx-boot_*.bb recipe from meta-freescale) and I

Re: [yocto] [meta-openssl102-fips][PATCH V3 4/16] classes/image-enable-fips.bbclass: enable user space fips mode in image

You are correct. I had found that earlier today. Anyway, the code has been verified as functional, and has been pushed. Thanks! --Mark On 9/25/19 9:35 PM, Hongxu Jia wrote: > Refer Fedora/RedHat's way >

Re: [yocto] Review request V2 0/16: [meta-openssl102-fips] Enable FIPS mode in Kernel and OpenSSH

On 9/25/19 2:23 AM, Hongxu Jia wrote: > Changed in V1: > - Follow Mark H's suggestions > > Hi Mark, > > Once openssh enables FIPS mode, openssh ptest will fail (mess of failure). > It seems the test case of upstream openssh does not consider FIPS mode > support. > I search fedora, there is

Re: [yocto] [meta-openssl102-fips][PATCH 14/15] openssh: add CAVS tests for FIPS validation

+this version download from: > + > http://pkgs.fedoraproject.org/cgit/rpms/openssh.git/plain/openssh-6.6p1-ctr-cavstest.patch > + (as of commit 991b66246f5151884b63c6d1232610a4569642a5) > + > +Makefile.in slightly modified for integration > + > +This is the makefile.in change for t

Re: [yocto] [meta-openssl102-fips][PATCH 9/15] openssh: port sshd_check_keys from oe-core

Please include the oe-core commit that this version was taken from. It'll be easier to uprev, if needed, if we need to. --Mark On 9/22/19 9:57 AM, Hongxu Jia wrote: > Signed-off-by: Hongxu Jia > --- > .../openssh/openssh/sshd_check_keys| 78 > ++ > 1 file

Re: [yocto] [meta-openssl102-fips][PATCH 5/15] openssh: add generation of HMAC checksums in pkg_postinst

Same comment here as in the fipscheck about the post install stuff. --Mark On 9/22/19 9:56 AM, Hongxu Jia wrote: > Refer > https://src.fedoraproject.org/rpms/openssh/c/d93958db19129e0f4615865eab22fb36e1f4fb8a > > Signed-off-by: Hongxu Jia > --- > recipes-connectivity/openssh/openssh_fips.inc

Re: [yocto] [meta-openssl102-fips][PATCH 4/15] fipscheck: enable fipscheck on target

On 9/22/19 9:56 AM, Hongxu Jia wrote: > Refer Fedora/RedHat's way > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/6.5_technical_notes/dracut > > Signed-off-by: Hongxu Jia > --- > recipes-connectivity/openssh/fipscheck_1.5.0.bb | 4 > 1 file changed, 4

Re: [yocto] [meta-openssl102-fips][PATCH 3/15] fipscheck: add generation of the checksums in pkg_postinst

On 9/22/19 9:56 AM, Hongxu Jia wrote: > Refer https://pagure.io/fipscheck/c/489bc3ab3f73707e12b6c2644d80af5ff6fbbf70 > > Signed-off-by: Hongxu Jia > --- > recipes-connectivity/openssh/fipscheck_1.5.0.bb | 18 ++ > 1 file changed, 18 insertions(+) > > diff --git

Re: [yocto] [meta-openssl102-fips][PATCH 2/15] openssh_8.%.bbappend: support fips 140-2

On 9/22/19 9:56 AM, Hongxu Jia wrote: > Signed-off-by: Hongxu Jia > --- > .../openssh/openssh/0001-openssh-8.0p1-fips.patch | 528 > + > recipes-connectivity/openssh/openssh_8.%.bbappend | 4 + > recipes-connectivity/openssh/openssh_fips.inc | 8 + > 3 files

Re: [yocto] [meta-openssl102-fips][PATCH 1/15] fipscheck: add 1.5.0

Please include the commit id of the Fedora version that was included. It will help us review changes in the future. On 9/22/19 9:56 AM, Hongxu Jia wrote: > Port it from fedora: > https://src.fedoraproject.org/rpms/fipscheck > > It is required by openssh fips. > > Signed-off-by: Hongxu Jia >

Re: [yocto] [meta-openssl102-fips][PATCH] README.build: add steps to include openssl102

On 9/17/19 1:37 AM, Hongxu Jia wrote: > The openssl fips only works with old openssl(<=1.0.2), > update steps to clarify it for Yocto and Wind River Linux Merged. > Signed-off-by: Hongxu Jia > --- > README.build | 8 +--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git

Re: [yocto] [meta-openssl102-fips][PATCH 2/2] README.build: add FAQ to support fips on arm/aarch64/x86

On 9/16/19 9:34 PM, Hongxu Jia wrote: > Signed-off-by: Hongxu Jia > --- > README.build | 36 > 1 file changed, 36 insertions(+) > > diff --git a/README.build b/README.build > index 9735028..bc8fcf3 100644 > --- a/README.build > +++ b/README.build > @@ -245,3

Re: [yocto] [meta-openssl102-fips][PATCH 1/2] README.build: update steps for communtiy

On 9/16/19 9:34 PM, Hongxu Jia wrote: > Since the layer is now published via the Yocto Project and > git.yoctoproject.org, we should update steps in README.build Merged. > Signed-off-by: Hongxu Jia > --- > README.build | 21 - > 1 file changed, 16 insertions(+), 5

Re: [yocto] [help] Multiconfig - Depending on Recipe multiple times

On 8/29/19 10:05 AM, Johannes Wiesböck wrote: > Hello Everyone, > > i am using Yocto on the thud branch to build images for a real-time This is not implemented in thud. Thud had multiconfig supported, but didn't yet allow for dependencies between configurations. Master has support for

Re: [yocto] Error in building new recipe for Jool network translator

On 6/6/19 11:46 AM, Gokul Raj wrote: > Hi Ross, > > Thanks for the suggestion. I have tried with inheriting autotools-brokensep > bbclass. Now bitbake got the path for compilation. But, bitbake compilation > refering to native kernel src path for module compilation. For your > information > this

Re: [yocto] prelink-cross with -fno-plt

ative relocations: 0 >       3268:                time needed to load objects: 696886 cycles (49.0%) > /usr/bin/execstack: no files given >       3268: >       3268:     runtime linker statistics: >       3268:                final number of relocations: 5 >       3268:     final numb

Re: [yocto] prelink-cross with -fno-plt

Sorry for my delayed reply. I was out on a business trip. Did you try this with the ld.so statistics to see if the relocations were indeed reduced at runtime? One of my worries with these changes (since I am not an ELF expert either) is that we make a change that doesn't actually do anything --

Re: [yocto] long time for starting sshd (wait for crng init done ?)

On 5/13/19 2:07 PM, s...@gmx.li wrote: > From yocto 2.5 to 2.7 I noticed a change in booting. The kernel stops for > around 85 seconds. > It seems to me that starting sshd takes time until crng init is done. > In 2.5 it doesn't wait for that. How can I avoid that? > Maybe I have to add that I use

Re: [yocto] [OE-core] patchwork

On 5/13/19 10:46 AM, Adrian Bunk wrote: > On Mon, May 13, 2019 at 10:32:48AM +0300, Mark Hatle wrote: >> On 5/12/19 9:04 PM, akuster808 wrote: >>> ok, so no Admins. This is unexceptionable. >>> >>> OE TSC and Board, I believe its your time to get involved. >

Re: [yocto] [OE-core] patchwork

On 5/12/19 9:04 PM, akuster808 wrote: > ok, so no Admins. This is unexceptionable. > > OE TSC and Board, I believe its your time to get involved. I've not used patchwork before, do you know who originally configured it? Was it Paul Eggleton, or Richard, or? If I have an idea who was originally

Re: [yocto] [OE-core] Git commit process question.

On 4/1/19 6:20 PM, akuster808 wrote: > > > On 4/1/19 4:02 PM, Richard Purdie wrote: >> On Mon, 2019-04-01 at 15:33 -0700, akuster808 wrote: >>> Hello, >>> >>> I have noticed a large number of git commits with no header >>> information being accepted. >> Can you be more specific about what "no

Re: [yocto] Thud: building SDK fails: cannot find -lssp

On 3/20/19 5:30 PM, Lukasz Zemla wrote: > Hello All, > > I am trying to build SDK using Yocto thud tagged 2.6.1. Toolchain from > meta-linaro (edb7ffc2a121df7596385595abe75180296103e0). Unfortunately it > fails during perl build, complaining about missing ssp_nonshared and ssp > libraries.

Re: [yocto] PREFERRED_VERSION ignored

On 3/11/19 12:46 PM, Marco wrote: > Hello, > using Yocto version 'rocko' I have a custom layer defining a new > recipe and a distro. > I have a recipe openssl_1.0.1u.bb in my meta-custom layer. > My meta-custom layer.conf has BBFILE_PRIORITY_meta-custom = "9" > > In my meta-custom layer I have a

Re: [yocto] [opkg-devel] [opkg-utils] Question: why update-alternatives from opkg-utils chooses /usr/lib to hold database?

On 3/5/19 10:44 PM, Alex Kiernan wrote: > On Tue, Mar 5, 2019 at 10:50 PM Richard Purdie > wrote: >> >> On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote: >>> >>> On 3/5/19 12:11 AM, ChenQi wrote: Hi All, Recently I'm dealing with issue from which some discussion

Re: [yocto] Removing busybox

On 2/27/19 11:06 AM, Tom Rini wrote: > On Wed, Feb 27, 2019 at 01:16:56PM +0100, Jean-Christian de Rivaz wrote: > >> Hi all, >> >> After reading the thread "Removing busybox completely from the generated >> image" I tested to reproduce the method but this doesn't work as expected. >> >> git clone

Re: [yocto] gitsm fetcher fixes in thud?

On 2/11/19 10:10 PM, Scott Murray wrote: > Hi, > > I'm working on upgrading Automotive Grade Linux (AGL) from rocko to thud, > and there's substantial git submodule breakage with the fetcher as it > stands in thud ATM. I've been doing tests with the current gitsm.py from > master with Mark's

Re: [yocto] Community support for any Yocto release

On 1/16/19 2:58 AM, Gaurang Shastri wrote: > Thanks Nicolas for the prompt answer and wiki page information. > > So as you said, "Typically, alongside the latest release the previous two > releases are also maintained.", do you mean any release will be maintained > for 1 > year by community?

Re: [yocto] Error while using PSEUDO

On 12/19/18 8:16 AM, madoga wrote: > Hello everyone,  > > I am trying to use pseudo due to I need to set my entire rootfs. I would like > to > ask you some questions about how to use it, considering that it does not seem > to > work. I am going to explain the process I have followed:  > > I

Re: [yocto] [OE-core] FILESYSTEM_PERMS_TABLE / fs-perms.txt

On 12/10/18 4:14 AM, madoga wrote: >> On 12/5/18 11:12 AM, madoga wrote: >> >>> Hello List, >>> I am trying to configure my entire filesystem by using >>> FILESYSTEM_PERMS_TABLES >>> variable pointing to my custom fs-perms.txt, but it does not work. While I >>> debugged package.bbclass looking

Re: [yocto] [OE-core] FILESYSTEM_PERMS_TABLE / fs-perms.txt

On 12/5/18 11:12 AM, madoga wrote: > Hello List, > > I am trying to configure my entire filesystem by using FILESYSTEM_PERMS_TABLES > variable pointing to my custom fs-perms.txt, but it does not work. While I > debugged package.bbclass looking for any error or failure, I found something > strange

Re: [yocto] meta-mingw: unable to run executables on Windows

On 11/14/18 11:01 PM, Khem Raj wrote: > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: >> >> On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle wrote: >>> >>> On 11/14/18 9:54 AM, Mark Hatle wrote: >>>> On 11/13/18 3:56 AM, Samuli Piippo wrote: >>&

Re: [yocto] meta-mingw: unable to run executables on Windows

On 11/14/18 9:54 AM, Mark Hatle wrote: > On 11/13/18 3:56 AM, Samuli Piippo wrote: >> Hi, >> >> I've just upgraded poky and meta-mingw layers from sumo to thud and as a >> result >> a lot of the executables in the toolchain no longer run correctly on Windo

Re: [yocto] meta-mingw: unable to run executables on Windows

On 11/13/18 3:56 AM, Samuli Piippo wrote: > Hi, > > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > result > a lot of the executables in the toolchain no longer run correctly on Windows. Which version of windows? > I've built meta-toolchain for

Re: [yocto] Yocto Add Layer Issue

On 11/6/18 2:25 PM, nick wrote: > Greetings All, > I am wondering why this error is occuring: > yocto-layer: command not found Do you mean "bitbake-layers"? --Mark > as I already sourced into my build with oe-init script and therefore add > wondering why it's not found. I checked the current

Re: [yocto] How to avoid stripping libthread_db to enable gdb thread debugging?

On 11/2/18 1:03 PM, Hui Liu wrote: > Hi, > > I add gdb to my recipe, and found gdb can't enable thread debugging. > > The warning from gdb is: > > warning: Unable to find libthread_db matching inferior's thread library, > thread > debugging will not be available > > After some investigation,

Re: [yocto] [selinux] sumo compilation

On 10/21/18 12:18 AM, Stefano Cappa wrote: > I reverted the commit as described and finally I'm able to build. > > However, after using -minimal version and booting with selinux=1 and > enforcing=0, when I run this command: "fixfiles -f -F relabel" I get this > error: > > Cleaning out /tmp >

Re: [yocto] [selinux] sumo compilation

On 10/18/18 9:49 AM, Sinan Kaya wrote: > CC'ing the selinux maintainers: > > I was told that using the master branch and reverting the e2fs change > (http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151) > > works on sumo. > > Stefano's

Re: [yocto] meta-oracle-java still maintained?

On 10/17/18 9:33 AM, Joshua Watt wrote: > I was wondering if meta-oracle-java is still maintained? It looks like > there haven't been any release branches created since pyro. > > We are looking at using it to provide virtual/java-native for some > build host tools we have that were written in

Re: [yocto] [prelink-cross] [PATCH] x86_64: allow prelinking of PIE executables with COPY relocs

On 10/10/18 3:50 PM, Sergei Trofimovich wrote: > COPY relocs are fine to have in PIE executables (as opposed to > shared libraries). > > By enabling prelink on PIEs we achieve a few goals: > - prelink more PIE files on system: nicer for uniformity, > - avoid spurious warnings about shared

Re: [yocto] [prelink-cross][PATCH] Support copy relocations in .data.rel.ro

other patches and then I'll be pushing to the staging tree. --Mark > On Fri, Oct 12, 2018 at 10:00 AM Mark Hatle <mailto:mark.ha...@windriver.com>> wrote: > > On 10/4/18 9:12 AM, Kyle Russell wrote: > > Hey Mark, > > > > Do you think this appr

Re: [yocto] [prelink-cross][PATCH] Support copy relocations in .data.rel.ro

On 10/4/18 9:12 AM, Kyle Russell wrote: > Hey Mark, > > Do you think this approach is reasonable?  If so, I have another patch I'd > like > to propose that would enable us to better catch error scenarios (like the last > two patches address) that we might encounter during do_image_prelink.  We

Re: [yocto] Layerindex - actions required for deleted repos?

On 10/4/18 2:33 AM, Andreas Müller wrote: > Hi, > > I am cleaning my github and want to remove some repos. One of them is > meta-gumstix-community - it is not maintained any more. > This layer is listed in layer-index. Will it be removed automatically > or are there steps I have to take? Just

Re: [yocto] [prelink-cross][PATCH] rtld: get machine from undef_map for protected symbols

On 9/28/18 9:55 AM, Kyle Russell wrote: > Avoids rtld segfault when _dl_lookup_symbol_x is called with NULL > for skip_map on a protected symbol relocation. > > Global protected symbols may not actually require a copy relocaton, > in which case skip_map is undefined, so use the undef_map to

Re: [yocto] Intel machine with 64 Bit kernel and 32 Bit user space

On 7/26/18 10:19 AM, Alexander Kanavin wrote: > 2018-07-26 14:56 GMT+02:00 Ayoub Zaki : >> Is it possible to define a MACHINE configuration with a 64 Bit kernel and 32 >> Bit user space ? >> >> The user space should not be using a x32 ABI. > > I think (but I am not sure), that you can do it with

Re: [yocto] Reg. rpm changelog

On 7/17/18 1:39 PM, Vikram Chhibber wrote: > Hi All, > > I use the rpm created from my recipe and I need to know if there is a way to > add > changelog to this rpm. I should be able to use "rpm -q --changelog" option to > display this changelog. > > Please let me know if this is possible. No.

Re: [yocto] Issue yocto strip the kernel module signature during packaging

On 6/13/18 12:10 PM, Mathieu Alexandre-Tétreault wrote: > Hello, > > I am working to activate the kernel module signature for in-tree and > out-of-tree packages. > While I was debugging the cause of the kernel complaining about unsigned > modules. > I noticed that yocto was stripping the

Re: [yocto] LIC_FILES_CHKSUM: spaces in file names

On 5/15/18 7:25 AM, Damien LEFEVRE wrote: > Hi, > > I have a base recipe generated with devtool. > > The package I build has several license files which contain space characters > in > the file names. > > LIC_FILES_CHKSUM = "file://COPYRIGHT.md;md5=b229ca0c79785e9e86311477e7bdd9ea \ >          

Re: [yocto] [meta-selinux][PATCH] libselinux: python-importlib is now part of python*-core

On 5/11/18 12:28 PM, Rudolf J Streif wrote: > Echoing this: may I ask what the current maintenance status of > meta-selinux is. It appears that no updates have been made for more than > 9 months. This is of course not to blame anybody but out of concern that > the layer is falling behind even more

Re: [yocto] [layerindex-web][PATCH 2/2] Add CSV export for layer recipes

On 5/6/18 10:35 PM, Paul Eggleton wrote: > Add the ability to export the recipe listing for a layer to a CSV file > for importing into external tools. At the moment we include name, > version and license, but there is a parameter that lets you specify the > fields to include in the URL if desired.

Re: [yocto] [Yocto] Prelink compilation for ZCU102

On 4/17/18 3:55 AM, Nicolas Salmin wrote: > Hello guys, > > Someone here have some information to build prelink recipe for ZCU102 board > because i'm not able to do it ... > > Hello guys, > > Someone here have some information to build prelink recipe for ZCU102 board > because i'm not able to

Re: [yocto] btrfs-tools Requires libgcc_s.so.1

On 3/8/18 4:10 PM, Marcelo E. Magallon wrote: > On Thu, Mar 08, 2018 at 03:16:44PM -0600, Mark Hatle wrote: > >> RDEPENDS are automatically promoted to DEPENDS (build-time). I would >> normally >> expect libgcc_s.so.1 to be present via the typical default depends. Does

Re: [yocto] btrfs-tools Requires libgcc_s.so.1

On 3/8/18 3:00 PM, Marcelo E. Magallon wrote: > Sorry to go off on a tangent: > > On Fri, Mar 04, 2016 at 04:12:54PM -0800, robert_jos...@selinc.com wrote: > root@test:~# btrfs scrub start / scrub started on /, fsid 79dc4fed-a0f7-43e2-b9e7-056b1a2c4cdd >> (pid=333) libgcc_s.so.1

Re: [yocto] Are Windows SDKs (mingw layer) supposed to work?

On 3/6/18 4:39 AM, Burton, Ross wrote: > Have you tried using 2.4 to identify when it broke?  Clearly we need to extend > the selftest so the mingw SDK is actually tested... > > Ross > > On 6 March 2018 at 05:32, Reyna, David >

Re: [yocto] useradd-staticids

On 2/23/18 10:37 AM, Anders Montonen wrote: > Hi, > > I'm looking into using the useradd-staticids class for reproducible > builds. Is there any way to delay the warning/error about missing ids > until a recipe is actually built rather than getting them during parsing? > Having to generate

Re: [yocto] useradd-example.bb

On 2/14/18 2:57 PM, Jeff Osier-Mixon wrote: > Can anyone help Jean-Pierre? This seems at first like a simple issue during > do_populate. Need more information. Are you creating new users and putting files in those user directories in /usr/share or elsewhere? The /usr/share hierarchy is

Re: [yocto] Installing Wind River Linux

On 1/30/18 3:15 AM, 永瀨桂 wrote: > Hi, > I'm trying to build the installer for using the WindRiverLinux9 with a > development board. > > I want to build the installer's image using the Intel-corei7-64 BSP, but > I can't build wrlinux-image-glibc-small like in the guide below. >

Re: [yocto] Removing /usr/src/debug from image

On 12/5/17 12:40 PM, Koehler, Yannick wrote: > Hi, > > I have edited my local.conf to remove the debug related EXTRA_IMAGE_FEATURES. > My rootfs still contains a /usr/src/debug folder, which I would like to get > rid of. This likely come from -dbg package inclusion, which I would like to >

Re: [yocto] Contribute meta-installer to yocto

On 11/28/17 9:45 AM, akuster808 wrote: > > > On 11/27/2017 09:20 AM, Mark Hatle wrote: >> On 11/21/17 3:24 PM, Burton, Ross wrote: >>> On 21 November 2017 at 08:55, Hongxu Jia <hongxu@windriver.com >>> <mailto:hongxu@windriver.com>> wrote: >

Re: [yocto] Contribute meta-installer to yocto

On 11/21/17 3:24 PM, Burton, Ross wrote: > On 21 November 2017 at 08:55, Hongxu Jia > wrote: > > If yocto is interested in this layer and will accept it, > I could send pull request or some one directly fetch > from above

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

On 11/8/17 1:08 PM, Paul Eggleton wrote: > On Thursday, 9 November 2017 4:42:50 AM NZDT Mark Hatle wrote: >> On 11/7/17 8:43 PM, Paul Eggleton wrote: >>> On Wednesday, 8 November 2017 11:47:49 AM NZDT Mark Hatle wrote: >>>> On 11/7/17 4:31 PM, Amanda Brindle wrote:

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

On 11/7/17 8:43 PM, Paul Eggleton wrote: > On Wednesday, 8 November 2017 11:47:49 AM NZDT Mark Hatle wrote: >> On 11/7/17 4:31 PM, Amanda Brindle wrote: >>> Use JavaScript to check if the search box for recipe search is >>> empty before querying the database. This wi

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

On 11/7/17 4:31 PM, Amanda Brindle wrote: > Use JavaScript to check if the search box for recipe search is > empty before querying the database. This will prevent the "502 > Bad Gateway" error that occurs when the query takes too long due > to the large list of recipes. Since there are so many

Re: [yocto] pseudo - few general questions

On 11/1/17 8:49 AM, Mark Hatle wrote: > On 11/1/17 4:17 AM, Pavlina Varekova wrote: >> Hi, >> thank you very much. It sounds good. So I tried replace fakechroot with >> pseudo. >> I read man pages and replace: >> >> FAKECHROOT_BASE="${DIR1}" fakec

Re: [yocto] pseudo - few general questions

On 11/1/17 4:17 AM, Pavlina Varekova wrote: > Hi, > thank you very much. It sounds good. So I tried replace fakechroot with > pseudo. > I read man pages and replace: > > FAKECHROOT_BASE="${DIR1}" fakechroot  command > > with: > > %{PATH/TO/PSEUDO/}bin/pseudo  -r "${DIR1}" -P %{PATH/TO/PSEUDO/}

Re: [yocto] pseudo - few general questions

On 10/16/17 7:16 AM, Pavlina Varekova wrote: > Hi, > I am evaluating to use pseudo in one project so I have several questions > regarding the tool. > > As I see in the official home for pseudo's git repository the last commit is > from 2017-04-13. Is pseudo maintained now and will it be in the

Re: [yocto] [meta-selinux][PATCH] policycoreutils: update AUDITH, PAMH

This is incorrect. You are not allowed to dynamically determine capabilities like this. Because if another component changes, the system has no way to determine if this package should also be recompiled. policycoreutils should be using 'PACKAGECONFIG', with an audit and pam option. Then set a

Re: [yocto] Framework to implement mirroring in Yocto

On 10/6/17 5:08 PM, Gutierrez, Hernan Ildefonso (Boise R, FW) wrote: > Hi, > >   > > We are planning to implement a mirror for both source code downloaded and > sscache in our work environment. > We mirror a ton of code for our customers. We have two types or mirrors that we deliver. Raw

Re: [yocto] Errors building with Windows Subsystem for Linux (aka Bash on Ubuntu on Windows)

On 9/28/17 8:28 AM, Bryan Evenson wrote: > Ross, > >   > > *From:*Burton, Ross [mailto:ross.bur...@intel.com] > *Sent:* Wednesday, September 27, 2017 6:43 PM > *To:* Bryan Evenson > *Cc:* yocto@yoctoproject.org > *Subject:* Re: [yocto] Errors building with Windows

Re: [yocto] [meta-selinux] Update announcement

; Chanho Park > > On Fri, 15 Sep 2017 at 6:27 AM Mark Hatle <mark.ha...@windriver.com > <mailto:mark.ha...@windriver.com>> wrote: > > I have pushed an update to meta-selinux to work with master.  A few key > changes: > > The oe-selinux and poky-se

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

On 9/18/17 2:48 AM, wenzong fan wrote: > > > On 09/14/2017 09:33 PM, Mark Hatle wrote: >> On 9/14/17 5:31 AM, wenzong fan wrote: >>> >>> >>> On 09/14/2017 08:07 AM, Mark Hatle wrote: >>>> On 9/12/17 9:19 PM, Mark Hatle wrote: >>>&g

[yocto] [meta-selinux] Update announcement

I have pushed an update to meta-selinux to work with master. A few key changes: The oe-selinux and poky-selinux distro configurations HAVE BEEN REMOVED! It is now up to the user to enable the components using the appropriate DISTRO_FEATURES as documented in the README file. (acl xattr pam

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

On 9/14/17 5:31 AM, wenzong fan wrote: > > > On 09/14/2017 08:07 AM, Mark Hatle wrote: >> On 9/12/17 9:19 PM, Mark Hatle wrote: >>> On 9/12/17 9:06 PM, wenzong fan wrote: >>>> On 09/12/2017 06:59 PM, Chanho Park wrote: >>>>> Hi, >>>&

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

On 9/12/17 9:19 PM, Mark Hatle wrote: > On 9/12/17 9:06 PM, wenzong fan wrote: >> On 09/12/2017 06:59 PM, Chanho Park wrote: >>> Hi, >>> >>> I can't apply this patch on top of the master branch. Which revision did >>> you make the patches? >&

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

On 9/12/17 9:06 PM, wenzong fan wrote: > On 09/12/2017 06:59 PM, Chanho Park wrote: >> Hi, >> >> I can't apply this patch on top of the master branch. Which revision did >> you make the patches? > > Oops, that's my fault. I did a "sed -i -e 's/Subject: [/Subject: > [meta-selinux][/g' 00*" to

Re: [yocto] [meta-selinux] krogoth support

On 9/12/17 1:02 PM, Reach, Jonathon A wrote: > Hello, > >   > > I currently have a krogoth based project that I need to add the meta-selinux > layer to. > (I've replied this offlist, but figured it should go to the list as well...) Currently we do not have a krogoth branch. I never worked on

Re: [yocto] Suitable machine for yocto

On 9/10/17 2:31 PM, Alex Lennon wrote: > > > On 10/09/2017 19:17, Mark Hatle wrote: >> On 9/10/17 11:14 AM, Alex Lennon wrote: >>> >>> On 10/09/2017 17:06, Mark Hatle wrote: >>>> On 9/10/17 2:00 AM, Usman Haider wrote: >>>>> Hi

Re: [yocto] Suitable machine for yocto

On 9/10/17 11:14 AM, Alex Lennon wrote: > > > On 10/09/2017 17:06, Mark Hatle wrote: >> On 9/10/17 2:00 AM, Usman Haider wrote: >>> Hi, >>> >>> Can someone please recommend some good machine for yocto environment and >>> building sdks. I am in

Re: [yocto] Suitable machine for yocto

On 9/10/17 2:00 AM, Usman Haider wrote: > Hi, > > Can someone please recommend some good machine for yocto environment and > building sdks. I am interested in RAM, hard disk space, processor. You want fast I/O, as much RAM and as many (fast) cores as you can afford. I don't think there is a

  1   2   3   4   >