Update the sstate file's timestamps after it is installed, it will be
very useful for removing the old sstate file, especially, it's not easy
to remove when use the shared SSTATE_DIR, we can easily remove them with
this change, for example:
$ find state-cache -type f -ctime +10 -exec rm -f {} \;
The following changes since commit 4c0a9ccbad2889b27b4b1d2ab91215a4bdcca3ce:
python-numpy: Fix build for mips64 (2014-09-01 18:00:32 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/ss
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the files paths to
make split successfully and add PACKAGECONFIG
Changed in V2:
The python-bindings requires swig-native as DEPENDS, and
swig-native is not in oe-core, so disable python-bindings
by default
//Hongxu
The following changes since commit a44006262cf3b810ec78b4cccd8076102a7a0f3e:
distro/poky: Add Debian 7.5 and 7.6 version as
Add PACKAGECONFIG to support --enable-python-bindings
Add PACKAGECONFIG to support lttng-ust
And python-bindings requires swig-native as DEPENDS, and
swig-native is not in oe-core, so disable python-bindings
by default
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
The following changes since commit 4c0a9ccbad2889b27b4b1d2ab91215a4bdcca3ce:
python-numpy: Fix build for mips64 (2014-09-01 18:00:32 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/IMAGE_ROOTFS_SIZE
Previously, when building core-image-minimal, the rootfs size would
default to 64M because we use '?=' in bitbake.conf and also '?=' in
core-image-minimal.bb.
The thing is, we'd like to have a default value for all images set
in bitbake.conf but still allow each image recipe to set its own
On 09/04/2014 03:27 PM, Chong Lu wrote:
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
Currently, perf can't split to perf-archive, perf-tests, perf-python
and
perf-perl. All files are included in perf package. Change the files
paths to
make
On Thu, 2014-09-04 at 15:27 +0800, Chong Lu wrote:
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the files
On Thu, 2014-09-04 at 16:06 +0800, Chong Lu wrote:
On 09/04/2014 03:27 PM, Chong Lu wrote:
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
Currently, perf can't split to perf-archive, perf-tests, perf-python
and
perf-perl. All files
On 09/04/2014 04:10 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 16:06 +0800, Chong Lu wrote:
On 09/04/2014 03:27 PM, Chong Lu wrote:
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
Currently, perf can't split to perf-archive, perf-tests,
On Thu, 2014-09-04 at 16:17 +0800, Chong Lu wrote:
On 09/04/2014 04:10 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 16:06 +0800, Chong Lu wrote:
On 09/04/2014 03:27 PM, Chong Lu wrote:
On 09/03/2014 06:42 PM, Richard Purdie wrote:
On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
On Thu, 2014-09-04 at 00:05 -0700, Robert Yang wrote:
Update the sstate file's timestamps after it is installed, it will be
very useful for removing the old sstate file, especially, it's not easy
to remove when use the shared SSTATE_DIR, we can easily remove them with
this change, for example:
On 09/04/2014 04:27 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 00:05 -0700, Robert Yang wrote:
Update the sstate file's timestamps after it is installed, it will be
very useful for removing the old sstate file, especially, it's not easy
to remove when use the shared SSTATE_DIR, we can
On Thu, 2014-09-04 at 16:49 +0800, Robert Yang wrote:
On 09/04/2014 04:27 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 00:05 -0700, Robert Yang wrote:
Update the sstate file's timestamps after it is installed, it will be
very useful for removing the old sstate file, especially, it's
On 2014-08-29 14:09, Richard Purdie wrote:
This adds a recipe which creates a tarball of a standalone image
creation tool. On the most part this is copying in our standard lib/bb
and lib/oe library functions. There is a modified base.bbclass and
bitbake.conf, ultimately we could refactor files
I remove the Smart channels because it helps me to retest using simpleremote.
I think I should comment that part but leave it there for future use.
isRPM test is being done in setupModule():
if package_rpm != oeRuntimeTest.tc.d.getVar(PACKAGE_CLASSES,
True).split()[0]:
On 09/04/2014 04:53 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 16:49 +0800, Robert Yang wrote:
On 09/04/2014 04:27 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 00:05 -0700, Robert Yang wrote:
Update the sstate file's timestamps after it is installed, it will be
very useful for
On 09/04/2014 06:27 PM, Robert Yang wrote:
On 09/04/2014 04:53 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 16:49 +0800, Robert Yang wrote:
On 09/04/2014 04:27 PM, Richard Purdie wrote:
On Thu, 2014-09-04 at 00:05 -0700, Robert Yang wrote:
Update the sstate file's timestamps after it
On 3 September 2014 18:27, Christopher Larson kerg...@gmail.com wrote:
+++ b/meta/recipes-devtools/ossp-uuid/ossp-uuid/ldflags.patch
Missing patch header.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
On 3 September 2014 18:27, Christopher Larson kerg...@gmail.com wrote:
+++ b/meta/recipes-bsp/setserial/setserial/ldflags.patch
Missing patch header.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
On 3 September 2014 18:27, Christopher Larson kerg...@gmail.com wrote:
+++ b/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.patch
Missing patch header.
-export SYS_INCLUDES=-I${STAGING_INCDIR}
-
inherit autotools-brokensep update-rc.d
+EXTRA_OEMAKE = \
+'CC=${CC}' \
On 3 September 2014 18:27, Christopher Larson kerg...@gmail.com wrote:
+++ b/meta/recipes-bsp/hostap/hostap-utils-0.4.7/ldflags.patch
Missing header.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
On 3 September 2014 18:27, Christopher Larson kerg...@gmail.com wrote:
+++ b/meta/recipes-kernel/blktrace/blktrace/ldflags.patch
Missing header.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
For images without ptest the packages are automatically installed alongside
ptest-runner. Log results are saved in ./results folder.
No cleanup is done for packages after the test is finished.
Signed-off-by: Lucian Musat georgex.l.mu...@intel.com
---
meta/lib/oeqa/runtime/_ptest.py | 124
Signed-off-by: Lucian Musat georgex.l.mu...@intel.com
---
meta/lib/oeqa/oetest.py | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py
index ed8b3b2..0b7e7dc 100644
--- a/meta/lib/oeqa/oetest.py
+++ b/meta/lib/oeqa/oetest.py
@@ -66,6 +66,13
A module for parsing results based logs like ptest, compliance and performance.
Supports breaking the logs into multiple sections and also provides a result
object to use the parser with.
The parser is initialized with the regex required to identify results and
section statements in the target
Hi,
Quick question of style for the community to bikeshed on: in the
general case should recipes be split into foo_1.2.bb and foo.inc, or
should they only split to bb/inc if there are multiple versions and
generally there should just be foo_1.2.bb.
Specifically I'm looking at the libunwind
On 30/08/2014 7:15 AM, Dan McGregor wrote:
From: Dan McGregor dan.mcgre...@usask.ca
ASan and TSan are useful debugging tools, enable them on the
target and add the packages to packagegroup-core-sdk.
Signed-off-by: Dan McGregor dan.mcgre...@usask.ca
---
On 09/04/2014 10:12 PM, Burton, Ross wrote:
Hi,
Quick question of style for the community to bikeshed on: in the
general case should recipes be split into foo_1.2.bb and foo.inc, or
should they only split to bb/inc if there are multiple versions and
generally there should just be foo_1.2.bb.
On 4 September 2014 08:33, Jonathan Liu net...@gmail.com wrote:
On 30/08/2014 7:15 AM, Dan McGregor wrote:
From: Dan McGregor dan.mcgre...@usask.ca
ASan and TSan are useful debugging tools, enable them on the
target and add the packages to packagegroup-core-sdk.
Signed-off-by: Dan McGregor
Hello,
This patch is sitting the the queue still. Is it being considered or has
it been dropped ?
- Armin
On 08/19/2014 11:05 PM, Armin Kuster wrote:
webbrowser is being compiled but not included in packaging.
Add webbrowser to python-netclient
Signed-off-by: Armin Kuster
On 5/09/2014 1:28 AM, Dan McGregor wrote:
On 4 September 2014 08:33, Jonathan Liu net...@gmail.com wrote:
On 30/08/2014 7:15 AM, Dan McGregor wrote:
From: Dan McGregor dan.mcgre...@usask.ca
ASan and TSan are useful debugging tools, enable them on the
target and add the packages to
On 09/04/2014 08:03 AM, Robert Yang wrote:
On 09/04/2014 10:12 PM, Burton, Ross wrote:
Hi,
Quick question of style for the community to bikeshed on: in the
general case should recipes be split into foo_1.2.bb and foo.inc, or
should they only split to bb/inc if there are multiple versions
Burton, Ross ross.bur...@intel.com writes:
Quick question of style for the community to bikeshed on: in the
general case should recipes be split into foo_1.2.bb and foo.inc, or
should they only split to bb/inc if there are multiple versions and
generally there should just be foo_1.2.bb.
On 4 September 2014 16:41, akuster808 akuster...@gmail.com wrote:
This is the same reason why I have split a bb into two parts when I submit
upgrades. I feel it makes reviewing easier the next time a package gets
upgraded. Trying to find the actual changes between a file being deleted and
the
On 4 September 2014 17:07, Enrico Scholz
enrico.sch...@sigma-chemnitz.de wrote:
.inc files make sense with current packaging because they are revision
control friendly. E.g. you can put the logic into .inc and follow its
history with 'git log' which is not possible when there are only the
Bump to *August 2014* release
Signed-off-by: Maxin B. John maxin.j...@enea.com
---
meta/recipes-extended/ltp/{ltp_20140422.bb = ltp_20140828.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-extended/ltp/{ltp_20140422.bb = ltp_20140828.bb} (100%)
diff --git
On 4 September 2014 15:12, Burton, Ross ross.bur...@intel.com wrote:
Quick question of style for the community to bikeshed on: in the
general case should recipes be split into foo_1.2.bb and foo.inc, or
should they only split to bb/inc if there are multiple versions and
generally there should
Hi,
Wrong one. Please ignore this patch.
On Thu, Sep 04, 2014 at 06:33:55PM +0200, Maxin B. John wrote:
Bump to *August 2014* release
Signed-off-by: Maxin B. John maxin.j...@enea.com
---
meta/recipes-extended/ltp/{ltp_20140422.bb = ltp_20140828.bb} | 0
1 file changed, 0 insertions(+), 0
On 09/04/2014 11:29 AM, Burton, Ross wrote:
On 4 September 2014 17:07, Enrico Scholz
enrico.sch...@sigma-chemnitz.de wrote:
.inc files make sense with current packaging because they are revision
control friendly. E.g. you can put the logic into .inc and follow its
history with 'git log' which
Peter A. Bigot p...@pabigot.com writes:
.inc files make sense with current packaging because they are revision
control friendly. E.g. you can put the logic into .inc and follow its
history with 'git log' which is not possible when there are only the
versioned .bb files.
You can follow
On Thu, Sep 4, 2014 at 7:00 PM, Enrico Scholz
enrico.sch...@sigma-chemnitz.de wrote:
Peter A. Bigot p...@pabigot.com writes:
.inc files make sense with current packaging because they are revision
control friendly. E.g. you can put the logic into .inc and follow its
history with 'git log'
Andreas Müller schnitzeltony-gM/ye1e23mwn+bqq9rb...@public.gmane.org
writes:
it's not only 'git log'; it is 'git blame' too and because git does not
support renaming of files natively, the 'git log --follow' method is
error prone and might compare the wrong files resp. fail completely when
On 4 September 2014 19:36, Enrico Scholz
enrico.sch...@sigma-chemnitz.de wrote:
Did you ever use 'git blame' for few lines most recipes have?
In other projects (e.g. linux kernel) I am using C-x v g in emacs very
often to see when/why a certain line was added. In some OE recipes I
would like
On 09/02/2014 05:53 AM, Chen Qi wrote:
Upgrade systemd from 213 to 216.
This broke me, because by 216 systemd started managing /etc/resolv.conf
which is fine except that it uses a static configuration in
/etc/systemd/resolved.conf, whereas in the 213 days I was getting
/etc/resolv.conf
On 4 September 2014 20:30, Peter A. Bigot p...@pabigot.com wrote:
Further investigation suggests that systemd-networkd is intended to do the
same sort of thing as connman, though so maybe I need to shoot that instead.
I have no answers, but just wanted to note that there now appears to be some
On 09/04/2014 09:26 AM, Burton, Ross wrote:
On 4 September 2014 16:41, akuster808 akuster...@gmail.com wrote:
This is the same reason why I have split a bb into two parts when I submit
upgrades. I feel it makes reviewing easier the next time a package gets
upgraded. Trying to find the actual
On 4 September 2014 09:37, Jonathan Liu net...@gmail.com wrote:
On 5/09/2014 1:28 AM, Dan McGregor wrote:
On 4 September 2014 08:33, Jonathan Liu net...@gmail.com wrote:
On 30/08/2014 7:15 AM, Dan McGregor wrote:
From: Dan McGregor dan.mcgre...@usask.ca
ASan and TSan are useful debugging
Hi,
This report is exactly from 3 years ago. Has this ever been resolved or looked
at? We have started seeing this a lot lately in our own distro based on Daisy
with 3.14 kernel when building with 12-24 threads. But it might not be release
specific or even OE specifig...
All the same symptoms
I have changed name of the Image Configurator tool to Machine Setup Tool.
Also we have decided to host the recipe in the meta-intel layer instead of the
oecore layer for the upcoming Yocto Project 1.7 release. And after further
stabilization the recipe will be migrated to oecore layer before
Hi:
I would like to integrate texinfo-4.8 into oe-core, it was
released on 2007, and too old, but it is a GPLv2 package. Does
anyone objects?
--
Best Reagrds,
Roy | RongQing Li
--
___
Openembedded-core mailing list
52 matches
Mail list logo
