[yocto] Release Candidate Build for yocto-2.1.rc1.rc1 now available.

A release candidate build for yocto-2.1.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 7d2b2f5b644a2729c75b8ecb38345c9668d2c8bb meta-fsl-arm :

Re: [yocto] Sharing Sstate cache among different platform architectures

On Apr 7, 2016 1:44 AM, "Burton, Ross" wrote: > > > On 6 April 2016 at 18:18, Santosh Y wrote: >> >> Can sstate cache be shared among builds for different architectures like x86 & PowerPC? > > Yes (and different host distros). > > Ross Thank you. --

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

On Wed, Apr 6, 2016 at 3:23 PM, Burton, Ross wrote: > > On 6 April 2016 at 20:55, Ronald Oakes wrote: >> >> For what it's worth, I may be able to work around this by using the >> Poky-Tiny distribution, which is closer to what I'll need for the >>

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

On 6 April 2016 at 20:55, Ronald Oakes wrote: > For what it's worth, I may be able to work around this by using the > Poky-Tiny distribution, which is closer to what I'll need for the > minimalist system we need in the end. > If you need a minimal system then you might want to

Re: [yocto] Sharing Sstate cache among different platform architectures

On 6 April 2016 at 18:18, Santosh Y wrote: > Can sstate cache be shared among builds for different architectures like > x86 & PowerPC? > > Yes (and different host distros). Ross -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

Alas, not legally (government contract). I might be able to burn them to CD, but I'd still have to bring them home to email them. For what it's worth, I may be able to work around this by using the Poky-Tiny distribution, which is closer to what I'll need for the minimalist system we need in the

[yocto] Sharing Sstate cache among different platform architectures

Hello, Can sstate cache be shared among builds for different architectures like x86 & PowerPC? Thanks. Santosh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

On 6 April 2016 at 16:45, Chris Trobridge wrote: > I will try to sort that out tomorrow (p...@yoctoproject.org, right?). > No, openembedded-c...@lists.openembedded.org Regarding python3, whenever I change the "--with-python" option to > something other than

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

> From: ross.bur...@intel.com > Date: Wed, 6 Apr 2016 12:22:39 +0100 > Subject: Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2 > To: christrobri...@hotmail.com > CC: yocto@yoctoproject.org > > > On 6 April 2016 at 12:19, Chris Trobridge >

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

On 6 April 2016 at 15:27, Ronald Oakes wrote: > Unfortunately, my build system is airgapped from the Internet, making > copying files into emails (or attaching them) extremely difficult. > Can you not put them on a USB stick? Ross --

[yocto] [prelink-cross] [patch] gather.c: fix out of bounds access in maybe_pie()

The buffer passed to maybe_pie() holds only an ELF header and space where one program header would fit (on 64bit), but the program header table can be bigger or may be located somewhere else. The function however loops over the program headers without checking their position; if it doesn't stop on

[yocto] Help Cross Compiling for AVR

Hi All, I am attempting to get the AVR Toolchain working inside of Yocto, but unfortunately I'm relatively new to Yocto and keep seeing various errors I cannot resolve. I was able to follow the instructions HERE to get everything

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

Unfortunately, my build system is airgapped from the Internet, making copying files into emails (or attaching them) extremely difficult. RonO On Wed, Apr 6, 2016 at 4:33 AM, Burton, Ross wrote: > > On 5 April 2016 at 23:17, Ronald Oakes wrote: >> >> I'm

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

On 6 April 2016 at 12:19, Chris Trobridge wrote: > This did the trick for python 2.7, and "from gi.repository import GObject" > works too. > Can you send a patch to add this dependency to the pygobject package? Ross --

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

Thanks Ross, This did the trick for python 2.7, and "from gi.repository import GObject" works too. It's still not installed for python 3.5. I will see if I did anything specific to make that happen but it's odd that it worked before. Regards,Chris From: ross.bur...@intel.com Date: Wed, 6 Apr

Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2

On 6 April 2016 at 11:53, Chris Trobridge wrote: > ImportError: No module named importlib > Looks like python-gobject needs to depend on python-importlib. Not sure why that isn't in -core to be honest. Can you add python-importlib to your image and see if it then

[yocto] Python GObject Errors on yocto-2.1_M3.rc2

for 2.7 but not at all for 3.5. To simplify things, I have built core-image-full-cmdline on genericx86-64 and this gives the same result as my image: =Poky (Yocto Project Reference Distro) 2.0+snapshot-20160406 genericx86-64 console genericx86-64 login: rootroot@genericx86-64

Re: [yocto] Python do_install fails on QEMUX86-64 and corei7-64 under Debian 8.0.3 isolated station

On 5 April 2016 at 23:17, Ronald Oakes wrote: > I'm basing off of poky-jethro-14.0.1.tar.bz as downloaded from > yoctoproject.org. I've also got meta-intel from the git of that name > to support the corei7, my eventual target. > The full compile and install logs would be

[yocto] [oe] Problem building apache2 with php5

I created an image in more than a year ago with apache2 and php5. Now when I pull in all updates since then I realise that mod_php has been moved from the modphp recipe in meta-webserver to the php recipe in meta-oe. I have created a php_5.6.12.bbappend file in which I have