ping
On 02/25/2014 10:50 AM, Lu Chong wrote:
On 02/24/2014 10:18 PM, Saul Wold wrote:
On 02/22/2014 07:54 AM, Chong Lu wrote:
Need to export these environment variables for python-config to work.
Can you clariy further as to what's broken? Has this not been
working in the past, or is this
The following changes since commit 49aad7da07e187f206e963001844605731b01247:
bitbake: runqueue: Remove use of waitpid on worker processes (2014-03-19
17:46:33 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-libsoup
There was a error about mips-gcc optimization while building
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled, the 2.45.92
have fixed this issue.
[YOCTO #5512]
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
.../libsoup/{libsoup-2.4_2.45.3.bb = libsoup-2.4_2.45.92.bb} | 4 ++--
On 03/24/2014 03:40 PM, Hongxu Jia wrote:
There was a error about mips-gcc optimization while building
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled, the 2.45.92
have fixed this issue.
Update the comments to make a clarity.
libsoup-2.4: upgrade to 2.45.92
There was an error about
On 24 March 2014 07:40, Hongxu Jia hongxu@windriver.com wrote:
There was a error about mips-gcc optimization while building
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled, the 2.45.92
have fixed this issue.
.92 means beta release in GNOME versioning, so not only is this a
new upstream
The following changes since commit 24979a1f7ecc155cf36f61ffb2d2a32c2fb64734:
busybox: disable fsck.minix and mkfs.minix (2014-03-23 09:08:54 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib chonglu/acl
The result of getfacl is sorted by user id.
In Centos or RHEL, bin user id is 1 and daemon user id is 2.
But in our image, bin user id is 2 and daemon user id is 1.
The patch fixes this issue to make ptest pass.
Signed-off-by: Chong Lu chong...@windriver.com
---
meta/recipes-support/attr/acl.inc
On 03/24/2014 04:09 PM, Burton, Ross wrote:
On 24 March 2014 07:40, Hongxu Jia hongxu@windriver.com wrote:
There was a error about mips-gcc optimization while building
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled, the 2.45.92
have fixed this issue.
.92 means beta release in GNOME
There was an error about mips-gcc optimization while compiling
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled.
The test code of libsoup-2.4 2.45.3 triggered gcc assert which located
in gcc/dwarf2out.c:20810:
...
20806 gcc_assert (prev
20807(CALL_P (prev)
20808
The following changes since commit 49aad7da07e187f206e963001844605731b01247:
bitbake: runqueue: Remove use of waitpid on worker processes (2014-03-19
17:46:33 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-libsoup
On 24 March 2014 07:57, Hongxu Jia hongxu@windriver.com wrote:
There was an error about mips-gcc optimization while compiling
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled.
The test code of libsoup-2.4 2.45.3 triggered gcc assert which located
in gcc/dwarf2out.c:20810:
...
20806
There might a failure when build util-linux with the meta-selinux layer:
[snip]
sys-utils/setpriv.c:21:20: fatal error: cap-ng.h: No such file or directory
#include cap-ng.h
^
compilation terminated.
[snip]
Use PACKAGECONFIG to fix the problem.
[YOCTO #6026]
Signed-off-by:
The following changes since commit 4a47c943a76e79af82d47d8fa83c6687e0d915a0:
busybox: disable fsck.minix and mkfs.minix (2014-03-23 09:08:49 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/util-linux
Executive Summary
=
A very rocky week but we now have consistent green builds on the
autobuilder.
1.6 Release Status
===
Over the last week things have stabilised a lot from my perspective.
Most of the major changes are now in or have at least been tested. In
We've a complex versioning scenario here which leads me to my limits. :(
There are two recipes. One for a shared library and one for an application
using this library.
Both use GNU autotools (so they have internal version information). For
continuous integration purposes both use AUTOREV.
At
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
We've a complex versioning scenario here which leads me to my limits. :(
There are two recipes. One for a shared library and one for an application
using this library.
Both use GNU autotools (so they have internal version
On 24.03.2014 13:35, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
We've a complex versioning scenario here which leads me to my limits. :(
There are two recipes. One for a shared library and one for an application
using this library.
Both use GNU autotools
On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote:
On 24.03.2014 13:35, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
We've a complex versioning scenario here which leads me to my limits. :(
There are two recipes. One for a shared library and one for
I copied a recipe from an old openembedded classic project into an oe-core
based one. It fetches from one of our many password-protected SVN
repositories. This used to work just fine, all you had to do was just run 'svn
something' on such a repo once and then svn would happily fetch from it.
Address the error
| checking for ZLIB... no
| checking for inflate in -lz... no
| configure: error: *** Working zlib library and headers not found ***
by ensuring zlib-native is in DEPENDS.
[YOCTO #5773]
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
diff --git
On 24.03.2014 13:53, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote:
On 24.03.2014 13:35, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
We've a complex versioning scenario here which leads me to my limits. :(
There are two
Please review the attached patch.
Many thanks,
Valentin
From 0a6844b003402164359c121706957c6f81e5fe79 Mon Sep 17 00:00:00 2001
From: Valentin Cobelea valentin.cobe...@enea.com
Date: Thu, 20 Mar 2014 15:36:43 +0100
Subject: [PATCH 1/1] [ppc64] Fixes a typo in tune config file for e6500.
This
On Mon, 2014-03-24 at 15:22 +0100, Steffen Sledz wrote:
On 24.03.2014 13:53, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote:
On 24.03.2014 13:35, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
debian.bbclass (debian package
On Mon, Mar 24, 2014 at 03:22:35PM +0100, Steffen Sledz wrote:
On 24.03.2014 13:53, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote:
On 24.03.2014 13:35, Richard Purdie wrote:
On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
We've a complex versioning
Without this dependency, changes to functions added to
SYSROOT_PREPROCESS_FUNCS do not change do_populate_sysroot's signature
and thus don't cause it to re-execute.
Fixes [YOCTO #5852].
Signed-off-by: Paul Eggleton paul.eggle...@linux.intel.com
---
meta/classes/staging.bbclass | 2 ++
1 file
The following changes since commit 4a47c943a76e79af82d47d8fa83c6687e0d915a0:
busybox: disable fsck.minix and mkfs.minix (2014-03-23 09:08:49 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/staging-fix
If we don't fix this, the recently added dependency from
do_populate_sysroot on functions in SYSROOT_PREPROCESS_FUNCS in
staging.bbclass triggers warnings that the get_binconfig_mangle
function contains tabs for all recipes that inherit binconfig.
Related to fix for [YOCTO #5852].
Signed-off-by:
On Sun, Mar 23, 2014 at 10:39 PM, Robert Yang liezhi.y...@windriver.comwrote:
+# 9) The recipe type that will be archived:
+#COPYLEFT_RECIPE_TYPES = 'type1 type2 ...'
+#The type can be: target native nativesdk cross crosssdk
cross-canadian.
Hmm, I wonder if we should note that the
This patch saves out provider information into the sysroot for all providers
except those in MULTI_PROVIDER_WHITELIST. This means that we will start seeing
warnings when two providers for the same thing are installed into the sysroot.
In the future those warnings can be turned into errors.
Hi,
This patch solves a problem we have been seeing when building both a .tar(.gz)
and .cpio(.gz) image, where the cpio job creates a file in the rootfs
directory. This event may happen while tar is running, which makes tar exit
indicating an error and thus aborting the build.
The only potential
The Linux kernel requires that initrd images contain a /init file for
the image to be used as an initrd, even if it is empty. Adding it into
the rootfs directory creates a race, that can upset tar when building
both a .tar and .cpio image file (tar: .: file changed as we read it).
Additionally,
As development on 1.6 finishes up, its time to think about what we
should be doing in the 1.7 cycle.
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow. Its a generic topic which I think covered multiple
areas (in no particular order):
* the ADT/SDK and how it
On Mon, 2014-03-24 at 16:09 +, Jonathan Austin wrote:
On 24/03/14 16:00, Richard Purdie wrote:
As development on 1.6 finishes up, its time to think about what we
should be doing in the 1.7 cycle.
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow.
On Mon, Mar 24, 2014 at 5:16 AM, Steffen Sledz sl...@dresearch-fe.de wrote:
We've a complex versioning scenario here which leads me to my limits. :(
There are two recipes. One for a shared library and one for an application
using this library.
Both use GNU autotools (so they have internal
From: Alexandru DAMIAN alexandru.dam...@intel.com
We add the PN to the buildstats event data in order to
proper select database task when multiple similar tasks
are executed for the same recipe file.
Signed-off-by: Alexandru DAMIAN alexandru.dam...@intel.com
diff --git
I can see this effort as a basis for re-writing the Models chapter of the
development manual.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Richard Purdie
Sent: Monday, March 24, 2014 9:01 AM
To: openembedded-core;
On Sat, 2014-03-22 at 23:25 -0300, João Henrique Ferreira de Freitas
wrote:
Hi Tom,
I am working to enhance the patches with your comments.
Em 21-03-2014 12:54, Tom Zanussi escreveu:
In any case, I think the connection between a command-line param and the
line in the .wks file should be
On 03/24/14 12:00, Richard Purdie wrote:
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow.
Maybe I'm using things incorrectly :-)
But I often find that I'm switching between building different images.
For example, one moment I might be building
On 03/24/2014 11:34 PM, Chris Larson wrote:
On Sun, Mar 23, 2014 at 10:39 PM, Robert Yang liezhi.y...@windriver.comwrote:
+# 9) The recipe type that will be archived:
+#COPYLEFT_RECIPE_TYPES = 'type1 type2 ...'
+#The type can be: target native nativesdk cross crosssdk
cross-canadian.
On Mon, Mar 24, 2014 at 6:43 PM, Robert Yang liezhi.y...@windriver.comwrote:
On 03/24/2014 11:34 PM, Chris Larson wrote:
On Sun, Mar 23, 2014 at 10:39 PM, Robert Yang liezhi.y...@windriver.com
wrote:
+# 9) The recipe type that will be archived:
+#COPYLEFT_RECIPE_TYPES = 'type1 type2
The problem is that do_configure.sigdata depends on STAMPS_DIR because:
do_configure - STAMPCLEAN - STAMPS_DIR
this will make the sigdata generated by STAMPS_DIR=/tmp/stps bitbake -S
recipe doesn't match the ones in our build dir, but it should. We can
add STAMPS_DIR or STAMPCLEAN to
The following changes since commit 09419cfb94b420628841bea8545e6a444856c3d5:
local.conf.sample.extended: update it for the archiver (2014-03-25 09:47:08
+0800)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/stamps_clean
On Mon, Mar 24, 2014 at 7:18 PM, Robert Yang liezhi.y...@windriver.comwrote:
The problem is that do_configure.sigdata depends on STAMPS_DIR because:
do_configure - STAMPCLEAN - STAMPS_DIR
this will make the sigdata generated by STAMPS_DIR=/tmp/stps bitbake -S
recipe doesn't match the ones
Hi Tom,
Almost done. I need to test and check some use cases.
Em 24-03-2014 17:13, Tom Zanussi escreveu:
I suppose using --label would be ok, though I don't really like to
overload things like this in general, and it forces the partitions to
have labels.
Nice, but I convinced myself to
The following changes since commit 12217d8620e434a88433e7a60ff7fa8a1b51c6b1:
meta/conf/bitbake.conf: add STAMPCLEAN to BB_HASHBASE_WHITELIST (2014-03-25
10:14:26 +0800)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/basefiles
If we run bitbake -S base-files today, and re-run it tomorrow with
nothing changed, we would see that the do_install.sigdata changes
because of:
do_intall - do_install_basefilesissue - DISTRO_VERSION - DATE
We had set:
IMAGE_NAME[vardepsexclude] += DATETIME
in meta/conf/bitbake.conf, we can set
On 03/25/2014 10:20 AM, Chris Larson wrote:
On Mon, Mar 24, 2014 at 7:18 PM, Robert Yang liezhi.y...@windriver.comwrote:
The problem is that do_configure.sigdata depends on STAMPS_DIR because:
do_configure - STAMPCLEAN - STAMPS_DIR
this will make the sigdata generated by
On 03/24/2014 05:06 PM, Burton, Ross wrote:
On 24 March 2014 07:57, Hongxu Jia hongxu@windriver.com wrote:
There was an error about mips-gcc optimization while compiling
libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled.
The test code of libsoup-2.4 2.45.3 triggered gcc assert which
On Mon, Mar 24, 2014 at 08:11:20PM -0400, Trevor Woerner wrote:
On 03/24/14 12:00, Richard Purdie wrote:
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow.
Maybe I'm using things incorrectly :-)
But I often find that I'm switching between building
49 matches
Mail list logo
