Re: [yocto] How to patch sysroots file?

2013-10-07 Thread Khem Raj
On Oct 7, 2013, at 6:53 AM, Ashish Dalela wrote: > > I am trying to build bridge-utils. During compilation, I get the error: > > /scratch/adalela/yocto/build/tmp/sysroots/qemux86/usr/include/linux/if_bridge.h:172:20: > error: field 'ip6' has incomplete typeIn file included from > ../libbridg

Re: [yocto] How to patch sysroots file?

2013-10-07 Thread Gaurang Shastri
>>So my question is: from where is the sysroots file coming? How should I generate the patch file for the sysroots Will, there is task called do_populate_systroot which will generate sysroots files/headers. If you want to generate the patch, you don't require to generate "sysroot patch" but you n

[yocto] Yocto Project Developer Day at ELCE

2013-10-07 Thread Jeff Osier-Mixon
I'm sure everyone attending ELCE has by now heard about DevDay, but I thought I would send one message to the list just in case. Please excuse the noise. The Yocto Project Developer Day at the Embedded Linux Conference in Edinburgh, Scotland is an all-day mini-conference with two tracks, all about

[yocto] Yocto-SPDX sync

2013-10-07 Thread Flanagan, Elizabeth
Attending: Jacob Matt Mark Beth Kate SPDX team moving forward. Mark Hatle working with team to help produce documentation. Fossology speed is a major issue (very single threaded). Presented at LinuxCon. Good feedback. Mark's plan is to activate within internal buildsystems within W

[yocto] How to patch sysroots file?

2013-10-07 Thread Ashish Dalela
I am trying to build bridge-utils. During compilation, I get the error: /scratch/adalela/yocto/build/tmp/sysroots/qemux86/usr/include/linux/if_bridge.h:172:20: error: field 'ip6' has incomplete typeIn file included from ../libbridge/libbridge.h:24:0 But, I don't see matching file paths in git pat

[yocto] WARNING: While compiling Strongswan Package

2013-10-07 Thread Amit Tomer
We have added some new patches for strongswan package but after we are seeing some waring message WARNING: strongswan: The compile log indicates that host include and/or library paths were used. We also tried to add "*EXTRA_OECONF = "--prefix=/any-old-thing"" to .bb file of strongswan* * * *But w

Re: [yocto] meta-toolchain-qt with Qt Creator

2013-10-07 Thread Laurentiu Palcu
Hi Diego, On Mon, Oct 07, 2013 at 08:18:00AM -0300, Diego Sueiro wrote: > 2013/10/7 Laurentiu Palcu > > Hi Diego, > It's a little more complicated than that. After building the toolchain, > all binaries have the default absolute path to the dynamic loader > (/opt/poky/...) hardco

Re: [yocto] meta-toolchain-qt with Qt Creator

2013-10-07 Thread Diego Sueiro
2013/10/7 Laurentiu Palcu > Hi Diego, > It's a little more complicated than that. After building the toolchain, > all binaries have the default absolute path to the dynamic loader > (/opt/poky/...) hardcoded in the elf INTERP section. This is easy to > change. However, other binaries may or may n

Re: [yocto] [PATCH] [eclipse-poky-juno] sdk.remotetools: use xterm for latencytop

2013-10-07 Thread Tudor Florea
Kind reminder. -Original Message- From: Tudor Florea [mailto:tudor.flo...@enea.com] Sent: Tuesday, October 01, 2013 18:15 To: yocto@yoctoproject.org Cc: Tudor Florea Subject: [PATCH] [eclipse-poky-juno] sdk.remotetools: use xterm for latencytop Use xterm instead of vt100 in order to avoi

[yocto] QA issue : bad RPATH error with runtime dependencies of package PCL

2013-10-07 Thread Anup Kini
Hi All, I am trying to build a recipe for PCL library, similar to the one that Lukas [1] has derived but for a older version because of some dependencies with other packages and support for ARM platform. 1. https://github.com/bulwahn/meta-ros/commit/2c1fb8dbc46f8bc3f3fe58fbdfb7b2c8f244431a I am

Re: [yocto] meta-toolchain-qt with Qt Creator

2013-10-07 Thread Laurentiu Palcu
Hi Diego, On Fri, Oct 04, 2013 at 05:26:06PM -0300, Diego Sueiro wrote: > Folks, > > I've found the issue. > I was installing the poky toolchain outside the default path > (/opt/opky/1.4.2). > After installing on default path, Qt creator was enable to find the right QT > version. I compiled an e