UCARP allows a couple of hosts to share common virtual IP addresses in
order to provide automatic failover. It is a portable userland
implementation of the secure and patent-free Common Address Redundancy
Protocol (CARP).
Signed-off-by: Yi Zhao
---
.../ucarp/ucarp/ucarp-configure-sha1.patch
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
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:
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 a
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 5:42 AM, Zhuoqun Cheng w
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, following thi
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 Conf
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 image
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
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
---
buildse
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
---
config/autobuilder.conf.example
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
---
config/autobuilder.conf.example| 1 +
.../autobuilder/buildsteps/DaftFlash.p
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
---
.../site-packages/autobuilder/buildsteps/RunSanityTest
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 insertions(+)
diff --git a/lib/pyth
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 not
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 as
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, following thi
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:
https://github.com/intel-aero/meta-intel-aero/wiki/Quicksta
18 matches
Mail list logo
