[yocto] xloadimage recipe

2019-04-04 Thread Belisko Marek
Hello, I was trying to write recipe for xloadimage (yes this SW is from 1993) and have some "custom" configuration step required. I already put some effort into that without success. Just curious: does anybody have recipe for that package to share? Thanks a lot. BR, marek -- as simple and prim

[yocto] Metadata is missing in some Python packages

2019-04-04 Thread Guenther Meyer
Hi, I added some python recipes for my application, and now I have the problem, that in some of the created packages the metadata is missing. For example, the package I have for Twisted 18.7 is one of those. When I use a python package like daphne, which is dependent on Twisted >= 18.7, then it wo

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

2019-04-04 Thread Alexander Kanavin
On Thu, 4 Apr 2019 at 02:39, Khem Raj wrote: > Definitely, and I agree that we should put relevant information in > commits, usually > the information about side effects if any, links to changelog etc. are > useful too > however, we should not enforce a behavior which could result in > redundancy

Re: [yocto] gdb built with musl libc segfault

2019-04-04 Thread Lluis Campos
On 03.04.2019 18:59, Khem Raj wrote: On Tue, Apr 2, 2019 at 4:51 AM Lluis Campos wrote: Hi all, This is my very first question in the Yocto mailing list. Very exited! Please let me know if I should use other list for this. I am building an image using musl libc instead of gnu libc. I am not

Re: [yocto] gdb built with musl libc segfault

2019-04-04 Thread Lluis Campos
Hi again, On 04.04.2019 12:58, Lluis Campos wrote: On 03.04.2019 18:59, Khem Raj wrote: On Tue, Apr 2, 2019 at 4:51 AM Lluis Campos wrote: Hi all, This is my very first question in the Yocto mailing list. Very exited! Please let me know if I should use other list for this. I am building a

[yocto] require and image.bbappend

2019-04-04 Thread Matteo Facchinetti
Hi, I encountered a problem when try to add packages in my image recipe, but I don't understernd if I wrong something or I have to do it in another way. In detail, in my common_layer there are: - image_base.bb : yocto base image - image_with_graphicsupport.bb : where include image_base.bb (

[yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Alexander Kanavin
As ptest-runner communicates with child processes via pipe2(), the corresponding channels are not attached to a pty. In that situation stdio facilities like printf() or fwrite() are fully buffered. If a ptest would use them, without bothering to fflush() the output, ptest-runner will only receive w

Re: [yocto] require and image.bbappend

2019-04-04 Thread Stefano Babic
Hi Matteo, On 04/04/19 15:35, Matteo Facchinetti wrote: > Hi, > > I encountered a problem when try to add packages in my image recipe, but > I don't understernd if I wrong something or I have to do it in another way. > > In detail, in my common_layer there are: >    - image_base.bb

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Alexander Kanavin
Bah, sorry, debugging got into the patch. Will resend. Alex On Thu, 4 Apr 2019 at 17:34, Alexander Kanavin wrote: > > As ptest-runner communicates with child processes via pipe2(), > the corresponding channels are not attached to a pty. In that > situation stdio facilities like printf() or fwri

[yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Alexander Kanavin
As ptest-runner communicates with child processes via pipe2(), the corresponding channels are not attached to a pty. In that situation stdio facilities like printf() or fwrite() are fully buffered. If a ptest would use them, without bothering to fflush() the output, ptest-runner will only receive w

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Joshua Watt
On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > As ptest-runner communicates with child processes via pipe2(), > the corresponding channels are not attached to a pty. In that > situation stdio facilities like printf() or fwrite() are fully > buffered. If a ptest would use them, withou

[yocto] Do you use ISO images generated by bitbake?

2019-04-04 Thread Burton, Ross
Hi, I'm looking for some users that use the ISO images generated by Bitbake (IMAGE_FSTYPE live or iso). Anyone out there? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Worries kernels supported

2019-04-04 Thread akuster808
Hello, I noticed there are 3 kernels in Warrior. 4.18, 4.19 an 5.0. Do we really need 4.18? I see its the default version for poky-tiny. 4.18 is EOL but maintained by Windriver. regards, Armin -- ___ yocto mailing list yocto@yoctoproject.org https:/

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Richard Purdie
On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > As ptest-runner communicates with child processes via pipe2(), > the corresponding channels are not attached to a pty. In that > situation stdio facilities like printf() or fwrite() are fully > buffered. If a ptest would use them, withou

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread richard . purdie
On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote: > Also, I don't see any ptest results for 2.6.2.rc3 on public > autobuilder. Do you have any plans to run them and share the results > on autobuilder? These were run separately but will run as part of any new stable release builds. The resul

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread akuster808
On 4/5/19 3:25 AM, richard.pur...@linuxfoundation.org wrote: > On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote: >> Also, I don't see any ptest results for 2.6.2.rc3 on public >> autobuilder. Do you have any plans to run them and share the results >> on autobuilder? > These were run separ

[yocto] [meta-security][PATCH 1/2] libldb: work around samba libldb packaging issues

2019-04-04 Thread Armin Kuster
Samba and libldb overlap in a few places. This is the simplest fix for now. Use "sssd" DISTRO_FEATUE to test and enable changes Signed-off-by: Armin Kuster --- recipes-support/libldb/libldb_%.bbappend | 1 + recipes-support/libldb/libldb_sssd.inc | 22 ++ 2 files changed,

[yocto] [meta-security][PATCH 2/2] sssd: add DISTRO_FEATURE sssd

2019-04-04 Thread Armin Kuster
Signed-off-by: Armin Kuster --- recipes-security/sssd/sssd_1.16.4.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-security/sssd/sssd_1.16.4.bb b/recipes-security/sssd/sssd_1.16.4.bb index 34bc8c8..d6a308c 100644 --- a/recipes-security/sssd/sssd_1.16.4.bb +++ b/reci

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread richard . purdie
On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote: > > On 4/5/19 3:25 AM, richard.pur...@linuxfoundation.org wrote: > > On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote: > > > Also, I don't see any ptest results for 2.6.2.rc3 on public > > > autobuilder. Do you have any plans to run them

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread Tim Orling
Just curious: all Perl modules in oe-core have ptest enabled, but only libxml-parser-perl is included in these test reports. Is it simply the only module in that image or is something else afoot? On Thu, Apr 4, 2019 at 3:29 PM wrote: > On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote: > > > >

[yocto] [meta-security][PATCH 1/2] ccs-tools: move to reciped-mac

2019-04-04 Thread Armin Kuster
Signed-off-by: Armin Kuster --- {recipes-security => recipes-mac}/ccs-tools/README | 0 {recipes-security => recipes-mac}/ccs-tools/ccs-tools_1.8.4.bb | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-mac}/ccs-tools/README (100%) rename {recip

[yocto] [meta-security][PATCH 2/2] libmspack: update to 0.10.1

2019-04-04 Thread Armin Kuster
For details see: https://github.com/kyz/libmspack/blob/master/libmspack/ChangeLog change compression to match that now being used from source Signed-off-by: Armin Kuster --- .../libmspack/{libmspack_0.9.1.bb => libmspack_0.10.1.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 delet

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread akuster
On 4/5/19 6:28 AM, Tim Orling wrote: > Just curious: all Perl modules in oe-core have ptest enabled, but only > libxml-parser-perl is included in these test reports. Is it simply the > only module in that image or is something else afoot? Is this what you are looking for ? pango              |

Re: [yocto] [meta-security][PATCH 2/2] sssd: add DISTRO_FEATURE sssd

2019-04-04 Thread Adrian Bunk
On Fri, Apr 05, 2019 at 03:47:46AM +0530, Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > recipes-security/sssd/sssd_1.16.4.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/recipes-security/sssd/sssd_1.16.4.bb > b/recipes-security/sssd/sssd_1.16.4.bb > index

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread Tim Orling
> On Apr 4, 2019, at 8:39 PM, akuster wrote: > > > > On 4/5/19 6:28 AM, Tim Orling wrote: >> Just curious: all Perl modules in oe-core have ptest enabled, but only >> libxml-parser-perl is included in these test reports. Is it simply the only >> module in that image or is something else af

[yocto] create a own fs file

2019-04-04 Thread Johann Obermayr
Hello, with wks we create a own image. This image can use boot.img, rootfs.tar.., ... Is there a way to create a own datafs.tar.gz file And put this file to /tmp/deploy/images// datafs.bb '#add file to datafs DATAFS_add_file = "file:myconf.cfg" DATAFS_add_file += "file:/path/other.cfg" my.wsk

Re: [yocto] [meta-security][PATCH 2/2] sssd: add DISTRO_FEATURE sssd

2019-04-04 Thread akuster808
On 4/5/19 10:29 AM, Adrian Bunk wrote: > On Fri, Apr 05, 2019 at 03:47:46AM +0530, Armin Kuster wrote: >> Signed-off-by: Armin Kuster >> --- >> recipes-security/sssd/sssd_1.16.4.bb | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/recipes-security/sssd/sssd_1.16.4.bb

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Mikko.Rapeli
On Thu, Apr 04, 2019 at 10:48:17PM +0100, Richard Purdie wrote: > On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > > As ptest-runner communicates with child processes via pipe2(), > > the corresponding channels are not attached to a pty. In that > > situation stdio facilities like prin

Re: [yocto] get_kernelversion_headers not replacing '_' by '-'

2019-04-04 Thread Dimitris Tassopoulos
The same also happens with the deb packager. But it works with rpm. For deb '_' is not allowed character, so I guess ithe same for ipkg. You need to either change the 'LOCALVERSION' of the kernel or use rpm. Dimitris On Thu, Apr 4, 2019 at 11:07 AM Fernando AE wrote: > Hello all, > > I discove

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread richard . purdie
On Fri, 2019-04-05 at 06:16 +, mikko.rap...@bmw.de wrote: > On Thu, Apr 04, 2019 at 10:48:17PM +0100, Richard Purdie wrote: > > On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > > > As ptest-runner communicates with child processes via pipe2(), > > > the corresponding channels are n

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

2019-04-04 Thread richard . purdie
On Thu, 2019-04-04 at 17:58 -0700, Tim Orling wrote: > Just curious: all Perl modules in oe-core have ptest enabled, but > only libxml-parser-perl is included in these test reports. Is it > simply the only module in that image or is something else afoot? Its probably the only one in the image. I

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

2019-04-04 Thread Mikko.Rapeli
On Fri, Apr 05, 2019 at 07:46:00AM +0100, richard.pur...@linuxfoundation.org wrote: > On Fri, 2019-04-05 at 06:16 +, mikko.rap...@bmw.de wrote: > > On Thu, Apr 04, 2019 at 10:48:17PM +0100, Richard Purdie wrote: > > > On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > > > > As ptest