Re: [yocto] bind: issue in trust anchor management can cause named to crash (CVE-2015-1349)

2015-03-12 Thread Sona Sarmadi 
Hi Alex,

Yes I agree with you but this is already a public CVE. Maybe in the future we 
will/should just discuss security related issues in the 
yocto-secur...@yoctoproject.org mailing 
list, but right now we don’t have many members so I copy to the 
yocto@yoctoproject.org list as well.

My intention is to make the list aware of security vulnerabilities/CVEs which 
keep coming all the time. I encourage everyone to do this. We will soon or 
later create a bug in Bugzilla if needed or just backport the CVE to our 
version or upgrade the recipes in the affected package to the version which is 
not vulnerable.

//Sona

From: Alexandru Vaduva [mailto:vaduvajanalexan...@yahoo.com]
Sent: den 12 mars 2015 00:28
To: Sona Sarmadi; yocto-secur...@yoctoproject.org
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] bind: issue in trust anchor management can cause named to 
crash (CVE-2015-1349)

Wouldn`t it be better for the bugs to be only mentioned on the security list?
It is my opinion that know about a risk before it is fixed could cause more 
harm then good.
What do you thing about this?


Alex Vaduva
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] Get rid of do_shared_workdir task

2015-03-12 Thread ed . bartosh 
> On Wed, Mar 11, 2015 at 11:30 PM, Bruce Ashfield
>  wrote:
>>
>> Why would you be working on a bug, that is currently assigned to me ..
>> without
>> even mentioning it ?
>
> Aha! I see the bug was updated right before the patch was sent. So
> assuming
> that you only started working on it right before that update and send ..
> we
> aren't too badly off.
>
> I still could have provided my status and feedback before hand though :)
>
OK, next time I will. I just started to work on this issue and decided to
send patch just to start conversation. Sorry for the mess.

Let's continue discussing this in the bug.

Ed
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] should bitbake manual mention other task flags like file-checksums, ...?

2015-03-12 Thread Robert P. J. Day 

  bitbake user manual, section 3.6, provides a list of task flags, but
there are a few others that aren't mentioned there, is it worth adding
them or are they adequately obscure that readers don't need to know
about them?

* [file-checksums]
* [lockfiles]
* [sstate-inputdirs]
* [sstate-outputdirs]
* [sstate-plaindirs]
* [sstate-lockfile-shared]

and i already mentioned that [recideptask] was missing from that list.
are there any others?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Release Candidate Build for yocto-1.6.3.rc1 now available.

2015-03-12 Thread Saul Wold 

On 03/11/2015 12:24 AM, Poky Build User wrote:


A release candidate build for yocto-1.6.3.rc1 is now available at:



Turns out we missed a patch that will require an rc2, please stand by on 
testing and wait for an RC2 build.


Sau!



http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.3.rc1


Please begin QA on this build as soon as possible.


Build hash information:
meta-intel : 38e9abf2551dd6c2f701d0dad0d84766800fd25c
meta-fsl-arm : 0c4de80867c3ab4e9682dd7802d3fd907d1e1a23
meta-minnow : 58fd55eb321a875d4e51c5c430de4d725ec9ba4c
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45
meta-fsl-ppc : 299f84cceccacd84651c1cefc1c34e66fb598a96
poky : 827dc7f12cf0d9f446c713a4a5b07a87146b77ab


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] is meta-yocto-kernel-extras still being used?

2015-03-12 Thread Robert P. J. Day 

  current dev manual refers to this layer in section 2.2, but it
doesn't look like much has happened with that repo in quite some time.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works

2015-03-12 Thread Minchev, Todor 
Hello Bryan,

On Wed, 2015-03-11 at 13:45 +, Bryan Evenson wrote:
> I am trying to get the Yocto Eclipse plug-in setup so that I can build my 
> application from Eclipse.  I am *almost* there, but the final build is not 
> working.  I'm assuming there are some path/rights issues somewhere in the 
> chain because I can build from the command line.  I'm looking for some help 
> in figuring out where the difference is.
> 
> I am using Fedora 21 64-bit for a host system.  I am using Eclipse Kepler; I 
> also have Eclipse Luna installed, but I had to install Eclipse Kepler since 
> another plugin I am using does not yet have support for Eclipse Luna.  I am 
> on poky/daisy HEAD and have been able successfully build my image (image 
> based on core-image-minimal with a few extra applications).  Under Eclipse 
> Kepler, I installed the pre-build plug-in from the Yocto Eclipse Update Site 
> as instructed in the Yocto Project Development Manual for Poky 1.6.2.  I am 
> using my existing toolchain in the build directory, so I issued "bitbake 
> meta-ide-support" to generate the cross-toolchain support.  I then followed 
> the instructions under "Extracting the Root Filesystem" in the ADT Manual to 
> extract the root filesystem.  Specifically, I sourced the newly created 
> environment script and then called "runqemu-extract-sdk 
>  ".  Then, from Eclipse 
> I setup the Yocto Project AD
>  T for a "Build System Derived Toolchain", I set the Toolchain Root Directory 
> to my Poky build directory, and I set the Sysroot location to my extracted 
> sysroot directory.
> 
> After the initial environment setup, from Eclipse I selected File->New->C 
> Project, and selected a "Hello World ANSI C Autotools Project" under the 
> "Yocto Project ADT Autotools Project" options.  For the new project, if I 
> select "Reconfigure Project" the configuration fails with the following error:
> 
>   checking whether the C compiler works... no
> 
> From checking config.log, here are the details on the build failure:
> 
>   configure:3289: checking whether the C compiler works
>   configure:3311: arm-poky-linux-gnueabi-gcc  -march=armv5te -marm 
> -mthumb-interwork -mtune=arm926ej-s --sysroot=$SDKTARGETSYSROOT  -g -O0  
> --sysroot=//extracted_sysroot_1.6.2  
> --sysroot=//extracted_sysroot_1.6.2  
> --sysroot=//extracted_sysroot_1.6.2 conftest.c  >&5

It appears that your toolchain is configured properly, however the  GNU
linker (ld) cannot find the libraries it needs to link the binary. 

I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"

There should be an environment setup file

//poky/poky-build/tmp/environment-setup-XX


If you open it you will see SDKTARGETSYSROOT environment variable. It
most likely points to a different sysroot path. Please change it to
point to the directory where you extracted your sysroot
(//extracted_sysroot_1.6.2), create a new project and see if
that builds OK.


>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find crt1.o: No such file or directory
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find crti.o: No such file or directory
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find crtbegin.o: No such file or directory
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find -lgcc
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find -lgcc_s
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find -lc
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find -lgcc
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find -lgcc_s
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find crtend.o: No such file or directory
>   
> //poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld:
>  cannot find crtn.o: No such file or directory
>   collect2: error: ld returned 1 exit status
>   configure:3315: $? = 1
>   configure:3353: result: no
>   configure: failed program was:
>   | /* confdefs.h */
>   | #define PACKAGE_NAME "adt_test_app"
>   | #define PACKAGE_TARNAME "adt_test_app"
>   | #define PACKAGE_VERSION "0.1.0"
>   | #define PACKAGE_STRI

[yocto] Release Candidate Build for yocto-1.6.3.rc2 now available.

2015-03-12 Thread Poky Build User 

A release candidate build for yocto-1.6.3.rc2 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.3.rc2


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 38e9abf2551dd6c2f701d0dad0d84766800fd25c 
meta-fsl-arm : 0c4de80867c3ab4e9682dd7802d3fd907d1e1a23 
meta-minnow : 58fd55eb321a875d4e51c5c430de4d725ec9ba4c 
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 
meta-fsl-ppc : 299f84cceccacd84651c1cefc1c34e66fb598a96 
poky : 6b8f7999c3e86d6e834af95ffe4c33d0d53db34a 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] should bitbake manual mention other task flags like file-checksums, ...?

2015-03-12 Thread Paul Eggleton 
Hi Robert,

On Thursday 12 March 2015 04:22:58 Robert P. J. Day wrote:
>   bitbake user manual, section 3.6, provides a list of task flags, but
> there are a few others that aren't mentioned there, is it worth adding
> them or are they adequately obscure that readers don't need to know
> about them?
> 
> * [file-checksums]

So, I'm in two minds about this one - it's largely an internal implementation 
detail, but if we did document how the file checksum stuff works then we should 
document the flag since most of the implementation for that is actually in 
BitBake - IIRC the only missing bit that is in OE is the bit that actually 
sets this flag on the appropriate task (do_fetch for OE).

> * [lockfiles]

Yes this one should be mentioned I think.

> * [sstate-inputdirs]
> * [sstate-outputdirs]
> * [sstate-plaindirs]
> * [sstate-lockfile-shared]

Shared state is pretty much entirely an OE concept rather than a BitBake one 
and thus these wouldn't be appropriate for the BitBake manual, but they ought 
to be covered in the shared state documentation in the Yocto Project Reference 
manual - they are at least referred to in examples but at the moment there is 
no actual reference for them (which we should have).
 
> and i already mentioned that [recideptask] was missing from that list.
> are there any others?

It's not unlikely that there are others, yes.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] is meta-yocto-kernel-extras still being used?

2015-03-12 Thread Bruce Ashfield 

On 2015-03-12 6:58 AM, Robert P. J. Day wrote:


   current dev manual refers to this layer in section 2.2, but it
doesn't look like much has happened with that repo in quite some time.



I'm the main user, and am simply lazy and pushing updates. That
being said, its use for others has been replaced by their own
layers, or bitbake/oe-core updates .. so it really doesn't need
to be in the manual any more.

Bruce


rday



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Linking of external libraries in the recipe

2015-03-12 Thread Priya Agarwal 
Hello,

I have taken a recipe for the package squid from OpenEmbedded.org and have
built it along with the kernel image.

Now I want to edit its recipe so that it will include some external
libraries.
But these libraries are the ones that are generated during the build. So
how do I edit the recipe to include those libraries?

Location of library:  ../yocto///libusdpaa.a

currently the do_compile task is failing as I have used an extra function
whose library I haven't included. Snippet of the error:

| main.cc: In function 'int SquidMainSafe(int, char**)':
| *main.cc:1259:10: error: 'of_init' was not declared in this scope*
| make[3]: *** [main.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| make[3]: Leaving directory
`/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory
`/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory
`/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
| make: *** [all-recursive] Error 1
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see
/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/temp/log.do_compile.28810
for further information)
ERROR: Task 799
(/media/NewVolume/yocto/meta-oe/meta-networking/recipes-daemons/squid/
squid_3.4.7.bb, do_compile) failed with exit code '1'

I have attached my recipe.


squid_3.4.7.bb
Description: Binary data
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] just one observation about bitbake manual, chapter 4, fetching

2015-03-12 Thread Robert P. J. Day 

  section 4.2, there is no mention of the "extract" parameter, used
with rpm and srpm. is it worth adding?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works

2015-03-12 Thread Bryan Evenson 
Todor,

> It appears that your toolchain is configured properly, however the  GNU 
> linker (ld) cannot find the libraries it needs to link the binary.
> I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> There should be an environment setup file
>
> //poky/poky-build/tmp/environment-setup-XX
>
> If you open it you will see SDKTARGETSYSROOT environment variable. It most 
> likely points to a different sysroot path.
> Please change it to point to the directory where you extracted your sysroot 
> (//extracted_sysroot_1.6.2),
> create a new project and see if that builds OK.

I've been having a few other issues with Eclipse (Install New Software menu 
item disappearing, other plugins disappearing after restarting, etc.), so I 
uninstalled eclipse, deleted my ~/.eclipse and workspace directories and 
re-installed Eclipse.  I need to run Eclipse Kepler (another plugin I'm using 
isn't ready for Eclipse Luna), so I followed these instructions for installing 
Eclipse by hand: 
http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-17-18-19-centos-red-hat-rhel-5-6.
   I also edited my environment setup script as suggested.  I then reinstalled 
all necessary plugins as described in the ADT manual.  I pointed the toolchain 
to my build directory and the sysroot location to my extracted sysroot.  I then 
followed the steps in the ADT manual to create a new Hello World Yocto ADT 
project.  I verified the SDKTARGETSYSROOT environment variable in the new 
project points to my extracted sysroot.  When I attempted to build, I get the 
following output:


Invoking autogen.sh in build directory: //workspace/adt_test/

Command-line environment variables:
 CFLAGS=" -g -O0  --sysroot=//extracted_sysroot_1.6.2" 
CXXFLAGS=" -g -O0  --sysroot=//extracted_sysroot_1.6.2" LDFLAGS=" 
--sysroot=//extracted_sysroot_1.6.2" CPPFLAGS=" 
--sysroot=//extracted_sysroot_1.6.2"

sh -c "//workspace/adt_test/autogen.sh 
--with-libtool-sysroot=//extracted_sysroot_1.6.2 
--target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi 
--build=x86_64-linux 
--with-libtool-sysroot=//extracted_sysroot_1.6.2"
aclocal: warning: couldn't open directory 
'//extracted_sysroot_1.6.2/usr/share/aclocal': No such file or 
directory
configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.ac:16: 
http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:20: installing './compile'
configure.ac:20: installing './config.guess'
configure.ac:20: installing './config.sub'
configure.ac:16: installing './install-sh'
configure.ac:16: installing './missing'
src/Makefile.am: installing './depcomp'
configure: loading site script //poky/meta/site/endian-little
configure: loading site script //poky/meta/site/arm-common
configure: loading site script //poky/meta/site/common-linux
configure: loading site script //poky/meta/site/common-glibc
configure: loading site script //poky/meta/site/arm-linux
configure: loading site script //poky/meta/site/common
configure: loading site script 
//poky/meta-openembedded/meta-oe/site/endian-little
configure: loading site script 
//poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/ncurses_config
configure: loading site script 
//poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/eglibc_config
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-poky-linux-gnueabi-strip... arm-poky-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... arm-poky-linux-gnueabi
checking how to print strings... printf
checking for style of include used by make... GNU
checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc  
-march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s 
--sysroot=$SDKTARGETSYSROOT
checking whether the C compiler works... no
configure: error: in `//workspace/adt_test':
configure: error: in `//workspace/adt_test':
configure: error: C compiler cannot create executables
configure: error: C compiler cannot create executables
See `config.log' for more details

Configuration failed with error

The bold lines are ones that I see as a potential problem.  First, the system 
couldn't find aclocal in my extracted sysroot.  I took a look in the directory 
listed, and aclocal is not in there.  I think the configure script also found 
the build system's install and mkdir (/usr/bin/install and /usr/bin/mkdir).  I 
don't know if there is supposed to be one of these in the extracted sysroot or 
not, but I thought it was worth noting.

On a possibly related topic, I noticed that the Eclipse Indexer is using the 
buil

Re: [yocto] Linking of external libraries in the recipe

2015-03-12 Thread Benjamin Esquivel 
On Thu, 2015-03-12 at 18:00 +0530, Priya Agarwal wrote:
> Hello,
> 
> 
> I have taken a recipe for the package squid from OpenEmbedded.org and
> have built it along with the kernel image. 
> 
> 
> Now I want to edit its recipe so that it will include some external
> libraries.
> But these libraries are the ones that are generated during the build.
> So how do I edit the recipe to include those libraries?
> 
Hi Priya, if you want to use a recipe and make some modifications to
it's behavior it is recommended that you do it via a .bbappend file

http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#using-bbappend-files

If the libraries are already generated during the build it might be a
case where you just DEPENDS_append = " " at
the .bbappend file. When the dependiencies are resolved prior your
recipe is built, the headers and libraries are placed in a special part
of the working directory that the recipes know where to look for (if
they don't deviate of the standard, of course). 

> 
> Location of
> library:  ../yocto///libusdpaa.a
> 
> 
> 
> currently the do_compile task is failing as I have used an extra
> function whose library I haven't included. Snippet of the error:
> 
> | main.cc: In function 'int SquidMainSafe(int, char**)':
> | main.cc:1259:10: error: 'of_init' was not declared in this scope
> | make[3]: *** [main.o] Error 1
> | make[3]: *** Waiting for unfinished jobs
> | make[3]: Leaving directory
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> | make[2]: *** [all-recursive] Error 1
> | make[2]: Leaving directory
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> | make[1]: *** [all] Error 2
> | make[1]: Leaving directory
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> | make: *** [all-recursive] Error 1
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile
> (see 
> /media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/temp/log.do_compile.28810
>  for further information)
> ERROR: Task 799
> (/media/NewVolume/yocto/meta-oe/meta-networking/recipes-daemons/squid/squid_3.4.7.bb,
>  do_compile) failed with exit code '1'
> 
> 
> I have attached my recipe.
> 
> 
> 


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bind: issue in trust anchor management can cause named to crash (CVE-2015-1349)

2015-03-12 Thread Benjamin Esquivel 
On Thu, 2015-03-12 at 07:35 +, Sona Sarmadi wrote:
> Hi Alex,
> 
>  
> 
> Yes I agree with you but this is already a public CVE. Maybe in the
> future we will/should just discuss security related issues in the
> yocto-secur...@yoctoproject.org mailing list, but right now we don’t
> have many members so I copy to the yocto@yoctoproject.org list as
> well. 
> 
I think this list is not published in the yocto lists page:

https://www.yoctoproject.org/tools-resources/community/mailing-lists

And, who would be able to subscribe to it? invite-only? public?
 
>  
> 
> My intention is to make the list aware of security
> vulnerabilities/CVEs which keep coming all the time. I encourage
> everyone to do this. We will soon or later create a bug in Bugzilla if
> needed or just backport the CVE to our version or upgrade the recipes
> in the affected package to the version which is not vulnerable.
> 
>  
> 
> //Sona
> 
>  
> 
> From: Alexandru Vaduva [mailto:vaduvajanalexan...@yahoo.com] 
> Sent: den 12 mars 2015 00:28
> To: Sona Sarmadi; yocto-secur...@yoctoproject.org
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] bind: issue in trust anchor management can cause
> named to crash (CVE-2015-1349)
> 
> 
>  
> 
> Wouldn`t it be better for the bugs to be only mentioned on the
> security list?
> 
> 
> It is my opinion that know about a risk before it is fixed could cause
> more harm then good.
> 
> 
> What do you thing about this?
> 
> 
>  
> 
> 
>  
> 
> 
> Alex Vaduva
> 
> 


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] clang cross compiler for OE available in meta-clang

2015-03-12 Thread Khem Raj 
Hi All,

Finally, clang/llvm is now in a working state as a cross compiler in meta-clang 
layer

https://github.com/kraj/meta-clang

Currently, It will build clang and stage it along with gcc cross compilers, 
default remains
as it is. If you wish to compile an additional recipe using clang you will add 
following two entries per recipe


TOOLCHAIN_pn- = "clang"
DEPENDS_append_pn- = " clang-cross "

to conf/clang.conf 

and it will start using clang for that component. Right now it only has one 
entry for ‘lzo’ :)
I am hoping to have this list grow soon

Right now, its only the cross compiler, which means compiler runtime is still 
same from gcc
and binutils are used in same way

Eventually, I will add compiler-rt and libc++ as well and also add 
cross-canadian builds of clang and make it cohabit in SDK
along with gcc.

If you would like to help trying/porting recipes to use clang/llvm or improve 
the layer, please lend your hand

Thanks for your time

-Khem

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Linking of external libraries in the recipe

2015-03-12 Thread Priya Agarwal 
>
> If the libraries are already generated during the build it might be a
> case where you just DEPENDS_append = " " at

he .bbappend file


I know where the libraries are but how do I make out which is the package.
(The needed '.a' files are in /usdpaa/git-r5/git/lib_powerpc/*)





On Thu, Mar 12, 2015 at 9:23 PM, Benjamin Esquivel <
benjamin.esqui...@linux.intel.com> wrote:

> On Thu, 2015-03-12 at 18:00 +0530, Priya Agarwal wrote:
> > Hello,
> >
> >
> > I have taken a recipe for the package squid from OpenEmbedded.org and
> > have built it along with the kernel image.
> >
> >
> > Now I want to edit its recipe so that it will include some external
> > libraries.
> > But these libraries are the ones that are generated during the build.
> > So how do I edit the recipe to include those libraries?
> >
> Hi Priya, if you want to use a recipe and make some modifications to
> it's behavior it is recommended that you do it via a .bbappend file
>
>
> http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#using-bbappend-files
>
> If the libraries are already generated during the build it might be a
> case where you just DEPENDS_append = " " at
> the .bbappend file. When the dependiencies are resolved prior your
> recipe is built, the headers and libraries are placed in a special part
> of the working directory that the recipes know where to look for (if
> they don't deviate of the standard, of course).
>
> >
> > Location of
> > library:  ../yocto///libusdpaa.a
> >
> >
> >
> > currently the do_compile task is failing as I have used an extra
> > function whose library I haven't included. Snippet of the error:
> >
> > | main.cc: In function 'int SquidMainSafe(int, char**)':
> > | main.cc:1259:10: error: 'of_init' was not declared in this scope
> > | make[3]: *** [main.o] Error 1
> > | make[3]: *** Waiting for unfinished jobs
> > | make[3]: Leaving directory
> >
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> > | make[2]: *** [all-recursive] Error 1
> > | make[2]: Leaving directory
> >
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> > | make[1]: *** [all] Error 2
> > | make[1]: Leaving directory
> >
> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
> > | make: *** [all-recursive] Error 1
> > | ERROR: oe_runmake failed
> > | ERROR: Function failed: do_compile
> > (see
> /media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/temp/log.do_compile.28810
> for further information)
> > ERROR: Task 799
> > (/media/NewVolume/yocto/meta-oe/meta-networking/recipes-daemons/squid/
> squid_3.4.7.bb, do_compile) failed with exit code '1'
> >
> >
> > I have attached my recipe.
> >
> >
> >
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Linking of external libraries in the recipe

2015-03-12 Thread Khem Raj 

> On Mar 12, 2015, at 5:30 AM, Priya Agarwal 
>  wrote:
> 
> Hello,
> 
> I have taken a recipe for the package squid from OpenEmbedded.org and have 
> built it along with the kernel image. 
> 
> Now I want to edit its recipe so that it will include some external libraries.
> But these libraries are the ones that are generated during the build. So how 
> do I edit the recipe to include those libraries?
> 
> Location of library:  ../yocto///libusdpaa.a

You need to write another recipe which is packaging/building these libraries 
and installing them into ${libdir}
then you will create a DEPENDS += “the new recipe name” in a bbappend for squid 
bb file.
then you will modify squid accordingly to consider linking these new libs may 
be via modifying LDFLAGS or going into the squid makefile system
and adding it there. 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Linking of external libraries in the recipe

2015-03-12 Thread Priya Agarwal 
Okay I think I understood. It has to be DEPENDS = "usdpaa" . Basically the
recipe which is building the libraries is
/meta-fsl-ppc/recipe-tools/usdpaa/usdpaa_git.bb.
Thanks.

On Thu, Mar 12, 2015 at 9:58 PM, Priya Agarwal <
priya_agar...@students.iitmandi.ac.in> wrote:

> If the libraries are already generated during the build it might be a
>> case where you just DEPENDS_append = " " at
>
> he .bbappend file
>
>
> I know where the libraries are but how do I make out which is the package.
> (The needed '.a' files are in /usdpaa/git-r5/git/lib_powerpc/*)
>
>
>
>
>
> On Thu, Mar 12, 2015 at 9:23 PM, Benjamin Esquivel <
> benjamin.esqui...@linux.intel.com> wrote:
>
>> On Thu, 2015-03-12 at 18:00 +0530, Priya Agarwal wrote:
>> > Hello,
>> >
>> >
>> > I have taken a recipe for the package squid from OpenEmbedded.org and
>> > have built it along with the kernel image.
>> >
>> >
>> > Now I want to edit its recipe so that it will include some external
>> > libraries.
>> > But these libraries are the ones that are generated during the build.
>> > So how do I edit the recipe to include those libraries?
>> >
>> Hi Priya, if you want to use a recipe and make some modifications to
>> it's behavior it is recommended that you do it via a .bbappend file
>>
>>
>> http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#using-bbappend-files
>>
>> If the libraries are already generated during the build it might be a
>> case where you just DEPENDS_append = " " at
>> the .bbappend file. When the dependiencies are resolved prior your
>> recipe is built, the headers and libraries are placed in a special part
>> of the working directory that the recipes know where to look for (if
>> they don't deviate of the standard, of course).
>>
>> >
>> > Location of
>> > library:  ../yocto///libusdpaa.a
>> >
>> >
>> >
>> > currently the do_compile task is failing as I have used an extra
>> > function whose library I haven't included. Snippet of the error:
>> >
>> > | main.cc: In function 'int SquidMainSafe(int, char**)':
>> > | main.cc:1259:10: error: 'of_init' was not declared in this scope
>> > | make[3]: *** [main.o] Error 1
>> > | make[3]: *** Waiting for unfinished jobs
>> > | make[3]: Leaving directory
>> >
>> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
>> > | make[2]: *** [all-recursive] Error 1
>> > | make[2]: Leaving directory
>> >
>> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
>> > | make[1]: *** [all] Error 2
>> > | make[1]: Leaving directory
>> >
>> `/media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/squid-3.4.7/src'
>> > | make: *** [all-recursive] Error 1
>> > | ERROR: oe_runmake failed
>> > | ERROR: Function failed: do_compile
>> > (see
>> /media/NewVolume/yocto/build_t4240qds_release/tmp/work/ppce6500-fsl_networking-linux/squid/3.4.7-r0/temp/log.do_compile.28810
>> for further information)
>> > ERROR: Task 799
>> > (/media/NewVolume/yocto/meta-oe/meta-networking/recipes-daemons/squid/
>> squid_3.4.7.bb, do_compile) failed with exit code '1'
>> >
>> >
>> > I have attached my recipe.
>> >
>> >
>> >
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works

2015-03-12 Thread Minchev, Todor 
On Thu, 2015-03-12 at 13:43 +, Bryan Evenson wrote:
> Todor,
>  
> > It appears that your toolchain is configured properly, however the
> GNU linker (ld) cannot find the libraries it needs to link the
> binary. 
> > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > There should be an environment setup file
> > 
> > //poky/poky-build/tmp/environment-setup-XX
> >
> > If you open it you will see SDKTARGETSYSROOT environment variable.
> It most likely points to a different sysroot path.
> > Please change it to point to the directory where you extracted your
> sysroot (//extracted_sysroot_1.6.2),
> > create a new project and see if that builds OK.
>  
> I've been having a few other issues with Eclipse (Install New Software
> menu item disappearing, other plugins disappearing after restarting,
> etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> directories and re-installed Eclipse.  I need to run Eclipse Kepler
> (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> these instructions for installing Eclipse by hand:
> http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-17-18-19-centos-red-hat-rhel-5-6.
>I also edited my environment setup script as suggested.  I then 
> reinstalled all necessary plugins as described in the ADT manual.  I pointed 
> the toolchain to my build directory and the sysroot location to my extracted 
> sysroot.  I then followed the steps in the ADT manual to create a new Hello 
> World Yocto ADT project.  I verified the SDKTARGETSYSROOT environment 
> variable in the new project points to my extracted sysroot.  When I attempted 
> to build, I get the following output:
>  
>  
> Invoking autogen.sh in build
> directory: //workspace/adt_test/
>  
> Command-line environment variables:
> CFLAGS=" -g -O0
> --sysroot=//extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> --sysroot=//extracted_sysroot_1.6.2" LDFLAGS="
> --sysroot=//extracted_sysroot_1.6.2" CPPFLAGS="
> --sysroot=//extracted_sysroot_1.6.2"
>  
> sh -c "//workspace/adt_test/autogen.sh
> --with-libtool-sysroot=//extracted_sysroot_1.6.2
> --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> --build=x86_64-linux
> --with-libtool-sysroot=//extracted_sysroot_1.6.2"
> aclocal: warning: couldn't open directory
> '//extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> or directory
> configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-arguments
> forms are deprecated.  For more info, see:
> configure.ac:16:
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
> configure.ac:20: installing './compile'
> configure.ac:20: installing './config.guess'
> configure.ac:20: installing './config.sub'
> configure.ac:16: installing './install-sh'
> configure.ac:16: installing './missing'
> src/Makefile.am: installing './depcomp'
> configure: loading site
> script //poky/meta/site/endian-little
> configure: loading site script //poky/meta/site/arm-common
> configure: loading site
> script //poky/meta/site/common-linux
> configure: loading site
> script //poky/meta/site/common-glibc
> configure: loading site script //poky/meta/site/arm-linux
> configure: loading site script //poky/meta/site/common
> configure: loading site
> script //poky/meta-openembedded/meta-oe/site/endian-little
> configure: loading site
> script 
> //poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/ncurses_config
> configure: loading site
> script 
> //poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/eglibc_config
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-poky-linux-gnueabi-strip...
> arm-poky-linux-gnueabi-strip
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... arm-poky-linux-gnueabi
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=
> $SDKTARGETSYSROOT
> checking whether the C compiler works... no
> configure: error: in `//workspace/adt_test':
> configure: error: in `//workspace/adt_test':
> configure: error: C compiler cannot create executables
> configure: error: C compiler cannot create executables
> See `config.log' for more details

This is a different error. There seems to be a mismatch between your
toolchain and rootfs. Could you please share the full name of 

my_built_image.tar.gz from

runqemu-extract-sdk 
"

>  
> Configuration failed with error
>  
> The bold lines are ones that I see as a potential problem.  First, the
> system couldn't find aclo

Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works

2015-03-12 Thread Bryan Evenson 


> -Original Message-
> From: Minchev, Todor [mailto:todor.minc...@intel.com]
> Sent: Thursday, March 12, 2015 1:50 PM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line
> build works
> 
> On Thu, 2015-03-12 at 13:43 +, Bryan Evenson wrote:
> > Todor,
> >
> > > It appears that your toolchain is configured properly, however the
> > GNU linker (ld) cannot find the libraries it needs to link the
> > binary.
> > > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > > There should be an environment setup file
> > >
> > > //poky/poky-build/tmp/environment-setup-XX
> > >
> > > If you open it you will see SDKTARGETSYSROOT environment variable.
> > It most likely points to a different sysroot path.
> > > Please change it to point to the directory where you extracted your
> > sysroot (//extracted_sysroot_1.6.2),
> > > create a new project and see if that builds OK.
> >
> > I've been having a few other issues with Eclipse (Install New Software
> > menu item disappearing, other plugins disappearing after restarting,
> > etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> > directories and re-installed Eclipse.  I need to run Eclipse Kepler
> > (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> > these instructions for installing Eclipse by hand:
> > http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-
> 17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script
> as suggested.  I then reinstalled all necessary plugins as described in the 
> ADT
> manual.  I pointed the toolchain to my build directory and the sysroot
> location to my extracted sysroot.  I then followed the steps in the ADT
> manual to create a new Hello World Yocto ADT project.  I verified the
> SDKTARGETSYSROOT environment variable in the new project points to my
> extracted sysroot.  When I attempted to build, I get the following output:
> >
> >
> > Invoking autogen.sh in build
> > directory: //workspace/adt_test/
> >
> > Command-line environment variables:
> > CFLAGS=" -g -O0
> > --sysroot=//extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> > --sysroot=//extracted_sysroot_1.6.2" LDFLAGS="
> > --sysroot=//extracted_sysroot_1.6.2" CPPFLAGS="
> > --sysroot=//extracted_sysroot_1.6.2"
> >
> > sh -c "//workspace/adt_test/autogen.sh
> > --with-libtool-sysroot=//extracted_sysroot_1.6.2
> > --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> > --build=x86_64-linux
> > --with-libtool-sysroot=//extracted_sysroot_1.6.2"
> > aclocal: warning: couldn't open directory
> > '//extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> > or directory
> > configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-
> arguments
> > forms are deprecated.  For more info, see:
> > configure.ac:16:
> >
> http://www.gnu.org/software/automake/manual/automake.html#Moderni
> ze-AM_005fINIT_005fAUTOMAKE-invocation
> > configure.ac:20: installing './compile'
> > configure.ac:20: installing './config.guess'
> > configure.ac:20: installing './config.sub'
> > configure.ac:16: installing './install-sh'
> > configure.ac:16: installing './missing'
> > src/Makefile.am: installing './depcomp'
> > configure: loading site
> > script //poky/meta/site/endian-little
> > configure: loading site script //poky/meta/site/arm-common
> > configure: loading site
> > script //poky/meta/site/common-linux
> > configure: loading site
> > script //poky/meta/site/common-glibc
> > configure: loading site script //poky/meta/site/arm-linux
> > configure: loading site script //poky/meta/site/common
> > configure: loading site
> > script //poky/meta-openembedded/meta-oe/site/endian-
> little
> > configure: loading site
> > script //poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/ncurses_config
> > configure: loading site
> > script //poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/eglibc_config
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for arm-poky-linux-gnueabi-strip...
> > arm-poky-linux-gnueabi-strip
> > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking build system type... x86_64-pc-linux-gnu
> > checking host system type... arm-poky-linux-gnueabi
> > checking how to print strings... printf
> > checking for style of include used by make... GNU
> > checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> > -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --
> sysroot=
> > $SDKTARGETSYSROOT
> > checking whether the C compiler works... no
> > configure: error: in `//workspace/adt_test':
> > configure: error: in `//workspace/adt_test':
> > configure: error: C com

[yocto] Cannot compile opencv with cmake.

2015-03-12 Thread Dalton Fury 
Hey,
I am trying to compile a c++ program which uses opencv on pokey. These are
the packages I have installed.
CORE_IMAGE_EXTRA_INSTALL += "cmake"

EXTRA_IMAGE_FEATURES += "tools-sdk"

When I run cmake,, I get this error.
http://pastebin.com/WifpRYXV

I followed the instructions given in this post:
http://stackoverflow.com/questions/8711109/could-not-find-module-findopencv-cmake-error-in-configuration-process
But still I get trouble:
http://pastebin.com/V7sSwP8r

I am new to yocto, and really need your help to proceed with my task.
Thankyou.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] running task only for native but not target?

2015-03-12 Thread Koehler, Yannick (HP Networking) 
I have a package that produce a binary that I need for native, and an C header 
file that I need for target.

I put the following do_install function to install appropriately the bin or 
header according to the class:

do_install_append_class-target () {
install -d ${D}${includedir}
install -m 0755 ${S}/ifrpc.h ${D}${includedir}
}

do_install_append_class-native() {
install -d ${D}${bindir}
install -m 0755 ${S}/ifrpcgen ${D}${bindir}
}

but is there a way for me to disable do_patch/do_configure/do_compile only when 
building for the target?  I have tried the following without success:

do_configure_class-target[noexec] = "1"
do_patch_class-target[noexec] = "1"
do_compile_class-target[noexec] = "1"

It appears the OVERRIDES do not apply here, any hint on how I can achieve this?

--
Yannick Koehler


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Cannot compile opencv with cmake.

2015-03-12 Thread Dalton Fury 
Hey, these are the packages that I included in the build for opencv support:
CORE_IMAGE_EXTRA_INSTALL += "libopencv-core-dev libopencv-highgui-dev
libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev"

On Fri, Mar 13, 2015 at 12:25 AM, Dalton Fury 
wrote:

> Hey,
> I am trying to compile a c++ program which uses opencv on pokey. These are
> the packages I have installed.
> CORE_IMAGE_EXTRA_INSTALL += "cmake"
>
> EXTRA_IMAGE_FEATURES += "tools-sdk"
>
> When I run cmake,, I get this error.
> http://pastebin.com/WifpRYXV
>
> I followed the instructions given in this post:
>
> http://stackoverflow.com/questions/8711109/could-not-find-module-findopencv-cmake-error-in-configuration-process
> But still I get trouble:
> http://pastebin.com/V7sSwP8r
>
> I am new to yocto, and really need your help to proceed with my task.
> Thankyou.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works

2015-03-12 Thread Bryan Evenson 
Todor,

> -Original Message-
> From: Minchev, Todor [mailto:todor.minc...@intel.com]
> Sent: Thursday, March 12, 2015 1:50 PM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line
> build works
> 
> On Thu, 2015-03-12 at 13:43 +, Bryan Evenson wrote:
> > Todor,
> >
> > > It appears that your toolchain is configured properly, however the
> > GNU linker (ld) cannot find the libraries it needs to link the
> > binary.
> > > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > > There should be an environment setup file
> > >
> > > //poky/poky-build/tmp/environment-setup-XX
> > >
> > > If you open it you will see SDKTARGETSYSROOT environment variable.
> > It most likely points to a different sysroot path.
> > > Please change it to point to the directory where you extracted your
> > sysroot (//extracted_sysroot_1.6.2),
> > > create a new project and see if that builds OK.
> >
> > I've been having a few other issues with Eclipse (Install New Software
> > menu item disappearing, other plugins disappearing after restarting,
> > etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> > directories and re-installed Eclipse.  I need to run Eclipse Kepler
> > (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> > these instructions for installing Eclipse by hand:
> > http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-
> 17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script
> as suggested.  I then reinstalled all necessary plugins as described in the 
> ADT
> manual.  I pointed the toolchain to my build directory and the sysroot
> location to my extracted sysroot.  I then followed the steps in the ADT
> manual to create a new Hello World Yocto ADT project.  I verified the
> SDKTARGETSYSROOT environment variable in the new project points to my
> extracted sysroot.  When I attempted to build, I get the following output:
> >
> >
> > Invoking autogen.sh in build
> > directory: //workspace/adt_test/
> >
> > Command-line environment variables:
> > CFLAGS=" -g -O0
> > --sysroot=//extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> > --sysroot=//extracted_sysroot_1.6.2" LDFLAGS="
> > --sysroot=//extracted_sysroot_1.6.2" CPPFLAGS="
> > --sysroot=//extracted_sysroot_1.6.2"
> >
> > sh -c "//workspace/adt_test/autogen.sh
> > --with-libtool-sysroot=//extracted_sysroot_1.6.2
> > --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> > --build=x86_64-linux
> > --with-libtool-sysroot=//extracted_sysroot_1.6.2"
> > aclocal: warning: couldn't open directory
> > '//extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> > or directory
> > configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-
> arguments
> > forms are deprecated.  For more info, see:
> > configure.ac:16:
> >
> http://www.gnu.org/software/automake/manual/automake.html#Moderni
> ze-AM_005fINIT_005fAUTOMAKE-invocation
> > configure.ac:20: installing './compile'
> > configure.ac:20: installing './config.guess'
> > configure.ac:20: installing './config.sub'
> > configure.ac:16: installing './install-sh'
> > configure.ac:16: installing './missing'
> > src/Makefile.am: installing './depcomp'
> > configure: loading site
> > script //poky/meta/site/endian-little
> > configure: loading site script //poky/meta/site/arm-common
> > configure: loading site
> > script //poky/meta/site/common-linux
> > configure: loading site
> > script //poky/meta/site/common-glibc
> > configure: loading site script //poky/meta/site/arm-linux
> > configure: loading site script //poky/meta/site/common
> > configure: loading site
> > script //poky/meta-openembedded/meta-oe/site/endian-
> little
> > configure: loading site
> > script //poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/ncurses_config
> > configure: loading site
> > script //poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/eglibc_config
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for arm-poky-linux-gnueabi-strip...
> > arm-poky-linux-gnueabi-strip
> > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking build system type... x86_64-pc-linux-gnu
> > checking host system type... arm-poky-linux-gnueabi
> > checking how to print strings... printf
> > checking for style of include used by make... GNU
> > checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> > -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --
> sysroot=
> > $SDKTARGETSYSROOT
> > checking whether the C compiler works... no
> > configure: error: in `//workspace/adt_test':
> > configure: error: in `//workspace/adt_test':
> > configure: error:

[yocto] File in append recipe not installed

2015-03-12 Thread p_j_r_m 
Hello

I'd like to add an append recipe for base-files in order to install a custom 
fstab.

In my system I already have this base-files recipes:

    
layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
    
layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files
├── base-files_3.0.14.bbappend
└── files
    └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

do_install_append() {
    echo "=== ${PN}-${PV} INSTALLING fstab "
    install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
}

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when 
I build the recipe with bitbake base-files it never gets called and my fstab 
file is not installed.
If the original recipe is base-files_3.0.14.bb, why append is 
base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i 
name and put FILESEXTRAPATHS



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] File in append recipe not installed

2015-03-12 Thread Gary Thomas 

On 2015-03-12 14:58, p_j_r_m wrote:

Hello

I'd like to add an append recipe for base-files in order to install a custom 
fstab.

In my system I already have this base-files recipes:

 
layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
 
layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files
├── base-files_3.0.14.bbappend
└── files
 └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

do_install_append() {
 echo "=== ${PN}-${PV} INSTALLING fstab "
 install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
}

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when 
I build the recipe with bitbake base-files it never gets called and my fstab 
file is not installed.
If the original recipe is base-files_3.0.14.bb, why append is 
base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i 
name and put FILESEXTRAPATHS


Instead of putting your fstab in 'files', put it in a directory
called 'base-files-3.0.14' which is where your FILESEXTRAPATHS
is looking.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] xserver-xf86-config: add rpi2 awareness

2015-03-12 Thread Andrei Gherzan 
On Wed, Mar 11, 2015 at 08:20:43PM +0100, Petter Mabäcker wrote:
> The following changes since commit 57c8e6bffbbef9b2331551093c3436303eb18386:
>
>   rpi-base.inc: Include the RPI2 DTB (2015-03-01 22:43:40 +0100)
>
> are available in the git repository at:
>
>   git://git.yoctoproject.org/poky-contrib petmab/rpi2_xserver_fix
>   
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi2_xserver_fix
>
> Petter Mabäcker (1):
>   xserver-xf86-config: add rpi2 awareness
>
>  .../xorg-xserver/xserver-xf86-config/{raspberrypi => rpi}/xorg.conf   | 0
>  .../xserver-xf86-config/{raspberrypi => rpi}/xorg.conf.d/10-evdev.conf| 0
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  rename recipes-graphics/xorg-xserver/xserver-xf86-config/{raspberrypi => 
> rpi}/xorg.conf (100%)
>  rename recipes-graphics/xorg-xserver/xserver-xf86-config/{raspberrypi => 
> rpi}/xorg.conf.d/10-evdev.conf (100%)

Merged. Thanks Petter.

--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/6] Restructure some recipes

2015-03-12 Thread Andrei Gherzan 
On Mon, Mar 02, 2015 at 12:05:21AM +0100, Andrei Gherzan wrote:
> The following changes since commit 57c8e6bffbbef9b2331551093c3436303eb18386:
>
>   rpi-base.inc: Include the RPI2 DTB (2015-03-01 22:43:40 +0100)
>
> are available in the git repository at:
>
>   git://git.yoctoproject.org/meta-raspberrypi ag-dev
>   http://git.yoctoproject.org/cgit.cgi/meta-raspberrypi/log/?h=ag-dev
>
> Andrei Gherzan (6):
>   bcm2835: More recipe to devtools
>   bootfiles: Move to recipes-bsp
>   firmware.inc: Move to recipes-bsp
>   vc-graphics: Move to recipes-graphics
>   rpi-basic-image: Define rpi SPLASH specific package
>   .gitignore: Ignore some stuff
>

Patch set merged to master.


--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] File in append recipe not installed

2015-03-12 Thread p_j_r_m 
I've tested it, but the problem is the same.My bbappend recipe is not even 
called ,so it does not matter what i put in it. Why is not called?
 

 El Jueves 12 de marzo de 2015 22:06, Gary Thomas  
escribió:
   

 On 2015-03-12 14:58, p_j_r_m wrote:
> Hello
>
> I'd like to add an append recipe for base-files in order to install a custom 
> fstab.
>
> In my system I already have this base-files recipes:
>
>      
>layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
>      
>layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend
>
> So I in my layer I have:
>
> layers/meta-mylayer/recipes/base-files
> ├── base-files_3.0.14.bbappend
> └── files
>      └── fstab
>
> and I add this base-files_3.0.14.bbappend content:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> SRC_URI_append = "file://fstab"
>
> do_install_append() {
>          echo "=== ${PN}-${PV} INSTALLING fstab "
>          install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
> }
>
> but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend 
> when I build the recipe with bitbake base-files it never gets called and my 
> fstab file is not installed.
> If the original recipe is base-files_3.0.14.bb, why append is 
> base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should 
> i name and put FILESEXTRAPATHS

Instead of putting your fstab in 'files', put it in a directory
called 'base-files-3.0.14' which is where your FILESEXTRAPATHS
is looking.

-- 

Gary Thomas                |  Consulting for the
MLB Associates              |    Embedded world

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


   -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] File in append recipe not installed

2015-03-12 Thread Gary Thomas 

On 2015-03-12 17:21, p_j_r_m wrote:

I've tested it, but the problem is the same.
My bbappend recipe is not even called ,so it does not matter what i put in it. 
Why is not called?


Please don't top-post :-(

How do you know that your bbappend isn't being used/called?  If you name it
incorrectly, e.g. base-files_3.0.99.bbappend, you should get an error telling
you that there is no base-files_3.0.99.bb which matches.  Hence if it's named
base-files_3.0.14.bbappend and you get no error, it *is* being used.

Please show exactly what is now in your layer (as below).  It's really easy
to make a mistake with a '_' instead of '-'.




El Jueves 12 de marzo de 2015 22:06, Gary Thomas  escribió:


On 2015-03-12 14:58, p_j_r_m wrote:


Hello

I'd like to add an append recipe for base-files in order to install a custom 
fstab.

In my system I already have this base-files recipes:

 
layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
 
layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files
├── base-files_3.0.14.bbappend
└── files
 └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

do_install_append() {
 echo "=== ${PN}-${PV} INSTALLING fstab "
 install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
}

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when 
I build the recipe with bitbake base-files it never gets called and my fstab 
file is not installed.
If the original recipe is base-files_3.0.14.bb, why append is 
base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i 
name and put FILESEXTRAPATHS



Instead of putting your fstab in 'files', put it in a directory
called 'base-files-3.0.14' which is where your FILESEXTRAPATHS
is looking.

--

Gary Thomas|  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto





--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Dizzy branch with Linux Kernel 3.19

2015-03-12 Thread Albert K 
Dear all,

I would like to know if it is possible to do a compile with Linux
Kernel 3.19.  I have tried the  PREFERRED_VERSION_linux-yocto_qemux86
= "3.19%"  in the local.conf and it does not work.

If possible, what need to be done to the this going.  Thanks.

Regards,
Albert.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Dizzy branch with Linux Kernel 3.19

2015-03-12 Thread Khem Raj 

> On Mar 12, 2015, at 9:21 PM, Albert K  wrote:
> 
> Dear all,
> 
> I would like to know if it is possible to do a compile with Linux
> Kernel 3.19.  I have tried the  PREFERRED_VERSION_linux-yocto_qemux86
> = "3.19%"  in the local.conf and it does not work.
> 
> If possible, what need to be done to the this going.  Thanks.
> 


you need to back port or write recipes for 3.19 kernel first

> Regards,
> Albert.
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Dizzy branch with Linux Kernel 3.19

2015-03-12 Thread Albert K 
Hi,

I am a bit confused as the 3.19 is listed in
http://git.yoctoproject.org.   BTW, how do I check which kernel
version is supported by a specific branch of yocto (eg dizzy, daisy).
Thanks.

Regards,
Albert.

On Fri, Mar 13, 2015 at 12:43 PM, Khem Raj  wrote:
>
>> On Mar 12, 2015, at 9:21 PM, Albert K  wrote:
>>
>> Dear all,
>>
>> I would like to know if it is possible to do a compile with Linux
>> Kernel 3.19.  I have tried the  PREFERRED_VERSION_linux-yocto_qemux86
>> = "3.19%"  in the local.conf and it does not work.
>>
>> If possible, what need to be done to the this going.  Thanks.
>>
>
>
> you need to back port or write recipes for 3.19 kernel first
>
>> Regards,
>> Albert.
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Dizzy branch with Linux Kernel 3.19

2015-03-12 Thread Khem Raj 

> On Mar 12, 2015, at 10:25 PM, Albert K  wrote:
> 
> Hi,
> 
> I am a bit confused as the 3.19 is listed in
> http://git.yoctoproject.org.   BTW, how do I check which kernel
> version is supported by a specific branch of yocto (eg dizzy, daisy).
> Thanks.
> 

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux?h=dizzy

> Regards,
> Albert.
> 
> On Fri, Mar 13, 2015 at 12:43 PM, Khem Raj  wrote:
>> 
>>> On Mar 12, 2015, at 9:21 PM, Albert K  wrote:
>>> 
>>> Dear all,
>>> 
>>> I would like to know if it is possible to do a compile with Linux
>>> Kernel 3.19.  I have tried the  PREFERRED_VERSION_linux-yocto_qemux86
>>> = "3.19%"  in the local.conf and it does not work.
>>> 
>>> If possible, what need to be done to the this going.  Thanks.
>>> 
>> 
>> 
>> you need to back port or write recipes for 3.19 kernel first
>> 
>>> Regards,
>>> Albert.
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Dizzy branch with Linux Kernel 3.19

2015-03-12 Thread Albert K 
Hi,

Thanks for the link.  One question,  for the kernel 3.17 the .bb
resolve to 3.17-rc7.   What can I find the release version for 3.17.
Thanks.

Regards,
Albert.

On Fri, Mar 13, 2015 at 1:29 PM, Khem Raj  wrote:
>
>> On Mar 12, 2015, at 10:25 PM, Albert K  wrote:
>>
>> Hi,
>>
>> I am a bit confused as the 3.19 is listed in
>> http://git.yoctoproject.org.   BTW, how do I check which kernel
>> version is supported by a specific branch of yocto (eg dizzy, daisy).
>> Thanks.
>>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux?h=dizzy
>
>> Regards,
>> Albert.
>>
>> On Fri, Mar 13, 2015 at 12:43 PM, Khem Raj  wrote:
>>>
 On Mar 12, 2015, at 9:21 PM, Albert K  wrote:

 Dear all,

 I would like to know if it is possible to do a compile with Linux
 Kernel 3.19.  I have tried the  PREFERRED_VERSION_linux-yocto_qemux86
 = "3.19%"  in the local.conf and it does not work.

 If possible, what need to be done to the this going.  Thanks.

>>>
>>>
>>> you need to back port or write recipes for 3.19 kernel first
>>>
 Regards,
 Albert.
 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
>>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto