[yocto] [PATCH] qt4-native: depend on icu-native to fix build on systems with icu >=59

Previously, qt4-native would use the system icu to build. Trying to build against a system ICU 59, however, fails with this root error: | In file included from /usr/include/unicode/uversion.h:30:0, | from tools/qlocale_icu.cpp:46: | /usr/include/unicode/umachine.h:347:13: error:

Re: [yocto] arm-poky-linux-gnueabi-gcc: Command not found

ravikiran j wrote: > > I am trying to build the linux kernel for odorid-xu3 board but i am getting > following errors for > bitbake linux-stable > > > DEBUG: Executing shell function do_compile > NOTE: make -j 4 HOSTCC=gcc HOSTCPP=gcc -E zImage > CC=arm-poky-linux-gnueabi-gcc -fuse-ld=bfd

Re: [yocto] The best way to change target architecture

On Tue, Jun 6, 2017 at 5:42 AM, Zhuoqun Cheng wrote: > Hi Yocto Experts, > > I'm fairly new to Yocto and I've already tried my best to search for > answers, but not happy with what I found. > > So here's the situation I've got: > > I'm using yocto to build the intel aero board image,

Re: [yocto] Yocto for NFS/SDN networking product

Generally individual components wrote there own component build systems using gmake, cmake, autotools etc. then they let the distros bundle it using their meta builders like rpm, dpkg etc. Yocto however is providing a mechanism to roll your own distro so many large projects now a days deploy it

[yocto] Minutes: Yocto Project Technical Team Meeting

Attendees: Armin, Joshua L., Joshua W., Pascal, Trevor, Stephen, Ross, Stephano, Richard, Michael, Juan, Paul, Mark, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.2.2 (Morty) rc1 is out of QA. We agreed to do a respin. YP 2.1.3 (Krogoth) has

[yocto] [yocto-autobuilder][PATCHv2 1/5] buildsteps/BuildImages: Setproperty BUILDIMAGES

In certain situations is need to know what images was built for example the DAFT executes flashing over certain image. [YOCTO #10604] Signed-off-by: Aníbal Limón --- lib/python2.7/site-packages/autobuilder/buildsteps/BuildImages.py | 3 +++ 1 file changed, 3

[yocto] [yocto-autobuilder][PATCHv2 2/5] buildsteps/RunSanityTests: Add support for simpleremote target

The testimage class supports a simpleremote target specifying the server and target ip to run tests over SSH. The main usage of this will in conjunction with the DAFT to make tests on real HW. [YOCTO #10604] Signed-off-by: Aníbal Limón ---

[yocto] [yocto-autobuilder][PATCHv2 4/5] autobuilder/buildsteps: Add DAFTFlash buildstep

This will execute daft flash cycle without reboot and prepare the dut for sanity tests. [YOCTO #10604] Signed-off-by: Aníbal Limón Signed-off-by: Monserrat Sedeno Signed-off-by: Edwin Plauchu ---

[yocto] [yocto-autobuilder][PATCHv2 3/5] autobuilder/buildsteps: Add DaftGetDevices step

This buildstep will copy the devices configuration from the worker and read it, in order to get daft ip an ssh port, to use later in RunSanityTests [YOCTO #10604] Signed-off-by: Aníbal Limón Signed-off-by: Monserrat Sedeno Signed-off-by: Edwin Plauchu

[yocto] [yocto-autobuilder][PATCHv2 5/5] buildset-config.yocto-qa: Add intel-corei7-64-daft buildset

This buildset is for support running sanity tests over a DUT like Minnowboard for the moment only builds core-image-sato, there is a need to make it configurable. Also the listo of the available devices are fixed into the UI as parameters. [YOCTO #10604] Signed-off-by: Aníbal Limón

Re: [yocto] [yocto-autobuilder][PATCHv2 4/5] autobuilder/buildsteps: Add DAFTFlash buildstep

This v2 fixes an small issue on variable name, DAFT_WORKER_WORKSPACE_DIR -> DAFT_WORKER_WORKSPACE. Cheers, Anibal On 06/06/2017 10:46 AM, Aníbal Limón wrote: > This will execute daft flash cycle without reboot and prepare the dut > for sanity tests. > > [YOCTO #10604] > > Signed-off-by: Aníbal

Re: [yocto] The best way to change target architecture

On Tue, 2017-06-06 at 08:42 -0400, Zhuoqun Cheng wrote: > Hi Yocto Experts, > > > I'm fairly new to Yocto and I've already tried my best to search for > answers, but not happy with what I found. > > > So here's the situation I've got: > > > I'm using yocto to build the intel aero board

Re: [yocto] The best way to change target architecture

On Tue, Jun 6, 2017 at 5:42 AM, Zhuoqun Cheng wrote: > Hi Yocto Experts, > > I'm fairly new to Yocto and I've already tried my best to search for > answers, but not happy with what I found. > > So here's the situation I've got: > > I'm using yocto to build the intel aero board image,

Re: [yocto] The best way to change target architecture

Thanks, Andre! That explains a lot. I got rid of the entire tmp directory and then rebuilt. And unfortunately I'm still running into the same problem... Looking at the error again (see below) On Tue, Jun 6, 2017 at 1:30 PM, Andre McCurdy wrote: > On Tue, Jun 6, 2017 at

Re: [yocto] The best way to change target architecture

Sorry for the previous message. Accidentally sent it out. Thanks, Andre! That explains a lot. I got rid of the entire tmp directory and then rebuilt. And unfortunately I'm still running into the same problem... I entered the directory shown in the error and did a 'file' on the binaries. They are

[yocto] The best way to change target architecture

Hi Yocto Experts, I'm fairly new to Yocto and I've already tried my best to search for answers, but not happy with what I found. So here's the situation I've got: I'm using yocto to build the intel aero board image, following this link:

Re: [yocto] The best way to change target architecture

Hi Leo and Khem, I just changed the MACHINE var to "intel-core2-32" (I assume it's the one in build/conf/local.conf. It was read-only and I added write permission) and it still gives me the same error. Here's some info that might be useful, before I change, when I do build, it prints: Build