Re: [yocto] Include all the native sdk packages built into sdk install script (populate_sdk)

2014-07-17 Thread Anooj Gopi
Dear Dennis, Thank you very much. I have tried "TOOLCHAIN_HOST_TASK" which works. But for some packages I could not find the bb file yet. eg. nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm generated by https://github.com/meta-qt5/meta-qt5/. Do you have any clue on how to find this out? Rega

[yocto] How to include native bitstream dependency in recipe?

2014-07-17 Thread Natural Groove
Hi, Im trying to crosscompile a framework that needs native bitstream dependency, but the configure does not find the headers. I was told to use ASSUME_PROVIDED, but i dont know how to give the path to bitstream in the recipe. Or is there a another way to deal with that like installing bitstream

Re: [yocto] libtool error when running adt_installer

2014-07-17 Thread Chong Lu
Hi Joseph, In adt-installer/opkg/build/opkg-svn/configure file, we have 8917 # Always use our own libtool. 8918 LIBTOOL='$(SHELL) $(top_builddir)/libtool' So, we should libtool rather than -libtool. Do you have any env variable to set LIBTOOL? In addition, I found your log: --2014-07-16 15:5

Re: [yocto] How to include native bitstream dependency in recipe?

2014-07-17 Thread Nicolas Dechesne
On Thu, Jul 17, 2014 at 10:37 AM, Natural Groove wrote: > Im trying to crosscompile a framework that needs native bitstream > dependency, but the configure does not find the headers. what is 'bitstream'? > I was told to use ASSUME_PROVIDED, but i dont know how to give the path to > bitstream in

Re: [yocto] libtool error when running adt_installer

2014-07-17 Thread Joseph Andrew de la Peña
Good day Chong, Thank you again for looking into my issue. Apparently, in the generated configure script: # Always use our own libtool. LIBTOOL='$(top_builddir)' LIBTOOL="$LIBTOOL/${host_alias}-libtool" Looked into the changes for this and there was a patch submitted to differentiate host alias

Re: [yocto] How to include native bitstream dependency in recipe?

2014-07-17 Thread Nicolas Dechesne
cc list. please let's have the discussion on the list On Thu, Jul 17, 2014 at 11:10 AM, Natural Groove wrote: > "biTStream is a set of C headers allowing a simpler access to binary > structures such as specified by MPEG, DVB, IETF, etc. " > (http://www.videolan.org/developers/bitstream.html) > >

[yocto] [PATCH] _json module arbitrary process memory read vulnerability

2014-07-17 Thread Daniel BORNAZ
python-native: _json module arbitrary process memory read vulnerability http://bugs.python.org/issue21529 Python 2 and 3 are susceptible to arbitrary process memory reading by a user or adversary due to a bug in the _json module caused by insufficient bounds checking. The sole prerequisites of t

[yocto] How to access the sysroot from CMake

2014-07-17 Thread Stefan Hofmann
Hi ! I have a package, which installs a VAPI-file in /usr/share/${PN}/${PN}.vapi. These files are required by the Vala-compiler (C#-like language for GObject) to interface with C-Code. However I cannot access it from a dependent package. What is the correct way to access files installed by othe

[yocto] wic status

2014-07-17 Thread Maciek Borzecki
Hi, There used to be an entry about wic in development manual back in 1.5.2: http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html This entry is gone in current documentation and there seems to be no mention of wic at all: https://www.yoctoproject.org/docs/current/dev-manual/dev-manua

Re: [yocto] wic status

2014-07-17 Thread Philip Balister
On 07/17/2014 08:25 AM, Maciek Borzecki wrote: > Hi, > > There used to be an entry about wic in development manual back in 1.5.2: > http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html I'm not sure where the docs are, but people are responding to bug reports about wic with patches :)

Re: [yocto] wic status

2014-07-17 Thread Paul Eggleton
On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote: > There used to be an entry about wic in development manual back in 1.5.2: > http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html > > This entry is gone in current documentation and there seems to be no > mention of wic at all:

Re: [yocto] How to include native bitstream dependency in recipe?

2014-07-17 Thread Natural Groove
I tried to make a recipe that just installs the file (not sure if this is exactly what you meant) it does generate the ipk with all files at the right place the recipe: do_install() { install -d ${D}${includedir} ${D}${includedir}/atsc ${D}${includedir}/dvb ${D}${includedir}/dvb/si ${D}${inclu

Re: [yocto] How to include native bitstream dependency in recipe?

2014-07-17 Thread Nicolas Dechesne
On Thu, Jul 17, 2014 at 3:11 PM, Natural Groove wrote: > > do_install() { > install -d ${D}${includedir} ${D}${includedir}/atsc ${D}${includedir}/dvb > ${D}${includedir}/dvb/si ${D}${includedir}/mpeg ${D}${includedir}/mpeg/psi > ${D}${includedir}/ietf > install -m 0755 common.h ${D}${includedir} >

Re: [yocto] wic status

2014-07-17 Thread Paul Eggleton
On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote: > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton < > paul.eggle...@linux.intel.com> wrote: > > On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote: > > > There used to be an entry about wic in development manual back in 1.5.2: > > > http:

Re: [yocto] wic status

2014-07-17 Thread Maciek Borzecki
On czw, 2014-07-17 at 16:48 +0300, Scott Rifenbark wrote: > wic was documented in the 1.5.x set and was not put into the 1.6 set. > I was told that it was going to change or be further completed so it > did not go in that development branch. Wic was never documented in > the 1.6 set. Makes sense

Re: [yocto] [OE-core] [PATCH] _json module arbitrary process memory read vulnerability

2014-07-17 Thread Saul Wold
On 07/17/2014 03:27 AM, Daniel BORNAZ wrote: python-native: _json module arbitrary process memory read vulnerability http://bugs.python.org/issue21529 Python 2 and 3 are susceptible to arbitrary process memory reading by a user or adversary due to a bug in the _json module caused by insufficien

Re: [yocto] wic status

2014-07-17 Thread Tom Zanussi
On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote: > On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote: > > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton < > > paul.eggle...@linux.intel.com> wrote: > > > On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote: > > > > There used to be a

Re: [yocto] wic status

2014-07-17 Thread Tom Zanussi
On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote: > On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote: > > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton < > > paul.eggle...@linux.intel.com> wrote: > > > On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote: > > > > There used to be a

Re: [yocto] wic status

2014-07-17 Thread Maciek Borzecki
On czw, 2014-07-17 at 09:18 -0500, Tom Zanussi wrote: > On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote: > > On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote: > > > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton < > > > paul.eggle...@linux.intel.com> wrote: > > > > On Thursday 17 July

Re: [yocto] wic status

2014-07-17 Thread Rifenbark, Scott M
So tomorrow I should have an updated version of that wic section in the dora branch of the docs. I will need Tom to look at it. I am making some changes based on the write up I got from that first email thread Tom sent out. Then, based on that copy in the 1.5.x docs, I will get the section in

Re: [yocto] wic status

2014-07-17 Thread Tom Zanussi
On Thu, 2014-07-17 at 19:38 +0200, Maciek Borzecki wrote: > On czw, 2014-07-17 at 09:18 -0500, Tom Zanussi wrote: > > On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote: > > > On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote: > > > > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton < > > >

[yocto] [yocto-docs][PATCH] kernel-dev manual: Update link to BitBake home page.

2014-07-17 Thread Robert P. J. Day
Signed-off-by: Robert P. J. Day --- as suggested by bill traynor. diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml index 297696c..38ef36d 100644 --- a/documentation/kernel-dev/kernel-dev-intro.xml +++ b/documentation/kernel-dev/kerne

[yocto] [yocto-docs][PATCH] kernel-dev-common.xml: Grammar fix.

2014-07-17 Thread Robert P. J. Day
Signed-off-by: Robert P. J. Day --- diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 555c8d8..5f28b82 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -85,7 +85,

[yocto] Adding prebuilt binaries/libraries to /usr/bin or/usr/lib on rootfs

2014-07-17 Thread Meenakumari Shedole
Hi all. I have few prebuilt binaries and libraries, and I want to add them to the yocto build rootfs at the build itself. So Can any one please tell me the steps to add recipes or suggest me any other method for this. Thnaks in Advance. Regards Meena ::DISCLAIMER:: -