On Sat, 2014-03-29 at 17:04 -0300, Otavio Salvador wrote:
piglit and mesa-demos are not buildable in x11-less distros so we must
to add those only when opengl and x11 DISTRO_FEATURES are available.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
The following changes since commit 2a33669ee0bd8a5d79489cafbff7309320de8d36:
packagegroup-toolset-native: remove it (2014-03-29 00:12:30 -0400)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/gtk
The target gtk+3 does a native build in its native directory, we need
set proper FLAGS for it, otherwise, there might be build failures.
[YOCTO #6070]
Signed-off-by: Robert Yang liezhi.y...@windriver.com
---
.../gtk+/gtk+3/fix-flags-for-native.patch | 40
On Mon, Mar 17, 2014 at 11:03:06AM +, Paul Eggleton wrote:
On Monday 17 March 2014 10:38:05 Richard Purdie wrote:
On Mon, 2014-03-17 at 10:25 +0100, Martin Jansa wrote:
* useful when distro wants to collect build statistics from
all users/developers without any manual
On Sun, Mar 30, 2014 at 09:03:02AM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: 42c0eba4fac6b8bd28b58ec04574d04b0ab0c457
URL:
http://git.openembedded.org/?p=openembedded-core.gita=commit;h=42c0eba4fac6b8bd28b58ec04574d04b0ab0c457
Author:
On Sun, 2014-03-30 at 13:30 +0200, Martin Jansa wrote:
On Sun, Mar 30, 2014 at 09:03:02AM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: 42c0eba4fac6b8bd28b58ec04574d04b0ab0c457
URL:
On Sun, 2014-03-30 at 13:25 +0200, Martin Jansa wrote:
On Mon, Mar 17, 2014 at 11:03:06AM +, Paul Eggleton wrote:
On Monday 17 March 2014 10:38:05 Richard Purdie wrote:
On Mon, 2014-03-17 at 10:25 +0100, Martin Jansa wrote:
* useful when distro wants to collect build statistics from
On Sun, Mar 30, 2014 at 8:36 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Sun, 2014-03-30 at 13:30 +0200, Martin Jansa wrote:
On Sun, Mar 30, 2014 at 09:03:02AM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit:
On 2014-03-30, 7:30 AM, Martin Jansa wrote:
On Sun, Mar 30, 2014 at 09:03:02AM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: 42c0eba4fac6b8bd28b58ec04574d04b0ab0c457
URL:
On 30 March 2014 02:31, Martin Jansa martin.ja...@gmail.com wrote:
Hi, sorry for longer e-mail, this is one of topic I would like to discuss
on OEDAM (http://openembedded.org/wiki/OEDAM), but having some feedback and
thoughts in advance will be very useful.
As people can notice from my State
On Sun, Mar 30, 2014 at 03:48:09PM +0100, Paul Barker wrote:
Are you discussing meta-oe alone here or all layers in meta-openembedded?
basically all of the layers which are included in my world builds, so it
includes all layers in meta-openembedded, most from meta-smartphone,
meta-browser,
On 30 March 2014 05:17, Khem Raj raj.k...@gmail.com wrote:
On Thu, Mar 27, 2014 at 5:53 AM, Paul Barker p...@paulbarker.me.uk wrote:
On 26 March 2014 22:12, Burton, Ross ross.bur...@intel.com wrote:
On 26 March 2014 22:04, Khem Raj raj.k...@gmail.com wrote:
There were interest in other threads
These are meant to be used by a master image, for a simple
initial setup.
The install scripts are similar to the default ones, but:
- custom partitioning, replaces the swap partiton with a second root filesystem
- adds labels to the partitions
- preconfigures a boot loader entry for the second
Add a custom recipe with custom initramfs and installers, that makes
it easy to deploy a master image for testing purposes.
We need a master image running on the target hardware, that should be a
known good build, with a set of utilities installed so that we use it
to deploy the images under test.
The purpose of this module is to deploy a test image on a EFI-enabled hardware
and run our runtime tests. A bit of background:
- testimage.bbclass uses the concept of TEST_TARGET which is a class name
that is responsible for target deploying. A layer can provide
it's own TEST_TARGET. Right now
Hello,
This is what I currently use for doing automated deployment
for a genericx86-64 image on NUC. More details on the commit
messages. There is nothing particular to genericx86-64,
it should work on any EFI-enabled device with gummiboot as bootloader.
Also see YB#1596 and it's sub-bug #5614
On 30 March 2014 16:14, Martin Jansa martin.ja...@gmail.com wrote:
On Sun, Mar 30, 2014 at 03:48:09PM +0100, Paul Barker wrote:
- We could create a new layer for unstable recipes which are 'use at
your own risk'. That may be a good place for recipes which don't work
on the jenkins builds but
On 30 March 2014 02:31, Martin Jansa martin.ja...@gmail.com wrote:
There are always 20+ failed tasks in those
big builds and just reading the numbers isn't good indicator of quality,
because sooner you break something in dependency tree, fewer recipes will
be actually tested, so fewer failed
Just out of curiosity,
http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches/log.world.20140329_001343.log/world_fixes.inc
includes the line:
inherit blacklist
But when I try, my build doesn't seem happy with this so I use the
following instead:
INHERIT += blacklist
I wonder
We do not DEPEND on libbsd, so we do not want to
build with it just because libutil.h is found by configure.
As noted in the patch, specifying --disable-libutil to
configure does not work, so we provide cached configure
variables.
Signed-off-by: Joe Slater jsla...@windriver.com
---
There was a nasty sstate hash corruption issue occurring where the
fact the testimage bbclass was inherited meant that the checksum
changed due to testimage.bbclass being confused with image.bbclass.
This patch anchors the bbclass names to avoid this confusion.
Signed-off-by: Richard Purdie
On 03/11/14 11:40, Stefan Stanacar wrote:
== is a bashism use = instead.
But the first line of this script is:
#/bin/bash
Shouldn't a bash script be allowed to have bash-isms??!
--
___
Openembedded-core mailing list
On 2014年03月28日 17:50, Richard Purdie wrote:
On Wed, 2014-03-26 at 18:15 +0800, Kai Kang wrote:
Replace ocf-linux with cryptodev-linux because linux-yocto use cryptodev-linux
to implement /dev/crypto.
Build for qemux86 and qemuarm. Test on qemux86.
This did break the build:
23 matches
Mail list logo
