The existing code in checkpkg from distrodata.bbclass had similar
functionality with fetch when searching for latest package version.
For packages that use svn protocol that part was rewrote in order
to use fetcher API.
It now calls latest_revision method from Svn class in fetch2 so
that it gets
On 11/08/2013 05:14 PM, Jonathan Liu wrote:
Hi Robert,
Is the queue visible publically?
Hi Jonathan,
See here please:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=robert/dora-next
// Robert
Regards,
Jonathan
On 4/11/2013 10:38 PM, Robert Yang wrote:
Hi Jonathan,
The following changes since commit ea92671d9823e3667d6ced7ac2af20f991da404d:
bitbake: cooker: replace w file opening mode with a mode (2013-11-12
17:01:37 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-nfs
By default, packagegroup-core-nfs do not depend on a certain architecture,
there will be qa warning while multilib enabled.
$ bitbake packagegroup-core-nfs
$ bitbake lib32-packagegroup-core-nfs
...
WARNING: The recipe lib32-packagegroup-core-nfs is trying to install files into
a shared area when
On 11/13/2013 08:30 PM, Burton, Ross wrote:
On 13 November 2013 10:08, Zhong Hongbo hongbo.zh...@windriver.com wrote:
+++
b/meta/recipes-connectivity/bluez/bluez4-4.101/fix-no-module-name-GObject-for-simple-agent.patch
@@ -0,0 +1,25 @@
+Fix No module name gi.repository and GObject for
first, in the list of Available IMAGE_FEATURES in
core-image.bbclass, should there be additional entries for
staticdev-pkgs and ptest-pkgs? for the sake of completeness?
also, i'm under the impression that the IMAGE_FEATURES is
*primarily* used to refer to package groups, but it also
This patch mainly aims to add optimisation for crosssdk setscene dependency
validating which we haven't handled in current logic, and which I think we
could have as we've already implemented to native/cross, although there
are albeit not many crossdk tasks, we could still get some performance
Interesting. I suppose this code wasn't tested on PowerPC machines
before. It is in the -bad package, so it does not surprise me, since
that is where new and unmaintained plugins are housed.
I'll discuss this with upstream, thanks.
On 2013-11-13 01:13, Saul Wold wrote:
On 11/08/2013 10:52
On 14 November 2013 10:47, Zhong Hongbo hongbo.zh...@windriver.com wrote:
What status should fill in Upstream-Status.
As I said, Inappropriate is suitable here.
Ross
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
---
meta/recipes-core/dbus/dbus.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index 5864643..0609d23 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -11,6 +11,7 @@
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
meta/recipes-support/liburcu/{liburcu_0.7.7.bb = liburcu_0.7.9.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/liburcu/{liburcu_0.7.7.bb = liburcu_0.7.9.bb}
(81%)
diff --git
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
.../lttng/{lttng-tools_2.3.0.bb = lttng-tools_2.3.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.3.0.bb =
lttng-tools_2.3.1.bb} (96%)
diff --git
This patch series provides minor version updates for the userspace components
of lttng 2.3. The corresponding update for the kernel side (lttng-modules
update to 2.3.3) will be provided by Otavio Salvador.
Paul Woegerer (3):
liburcu: Update to version 0.7.9
lttng-ust: Update to version 2.3.1
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
.../lttng/{lttng-ust_2.3.0.bb = lttng-ust_2.3.1.bb} | 8
1 file changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-ust_2.3.0.bb = lttng-ust_2.3.1.bb}
(80%)
diff --git
Even though this was in the last C-pull, for some reason, it didn't end
up in master... Didn't see any comments on it either. Or maybe I missed
them...
Thanks,
Laurentiu
On Wed, Nov 06, 2013 at 03:07:58PM +0200, Laurentiu Palcu wrote:
Flex needs m4 to run (see below) and, since the
From: Chen Qi qi.c...@windriver.com
This patch checks the validity of TMPDIR.
The TMPDIR must match the following regexp.
^/[a-zA-Z0-9\-_/.~]+$
Detailed tests about why I came up with this regexp are displayed at the end of
this cover letter.
A major reason for why TMPDIR cannot support many
From: Chen Qi qi.c...@windriver.com
TMPDIR must be an absolute path, otherwise, the build will fail.
Special characters in TMPDIR will also cause build failures.
This patch enables checking for the validity of TMPDIR.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/classes/sanity.bbclass
On Thu, 2013-11-14 at 21:07 +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
TMPDIR must be an absolute path, otherwise, the build will fail.
Special characters in TMPDIR will also cause build failures.
This patch enables checking for the validity of TMPDIR.
I couldn't find any up-to-date poky mirrors on github so I pushed my
own poky mirror[1]. Once I clean up my code, I will push it to my
repo.
I am also finally getting clang3.3 cross-compiler to compile using a
bitbake recipe quickly put together from the llvm3.3 recipe from
meta-oe.
The next step
On Thu, 2013-11-14 at 14:43 +0200, Laurentiu Palcu wrote:
Even though this was in the last C-pull, for some reason, it didn't end
up in master... Didn't see any comments on it either. Or maybe I missed
them...
In the target case, M4 should be compiled in as ${bindir}/m4 and there
should be no
On 2013-11-14 06:07, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
TMPDIR must be an absolute path, otherwise, the build will fail.
Special characters in TMPDIR will also cause build failures.
This patch enables checking for the validity of TMPDIR.
Signed-off-by: Chen Qi
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when my build
tree had the hyphen (-) in the path.
Paths with - in certainly work for me. If there are any recipes which
break in that situation then we should just fix them.
OE
On 2013-11-14 06:42, Phil Blundell wrote:
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when my build
tree had the hyphen (-) in the path.
Paths with - in certainly work for me. If there are any recipes which
break in that
On Thu, Nov 14, 2013 at 01:19:10PM +, Richard Purdie wrote:
On Thu, 2013-11-14 at 14:43 +0200, Laurentiu Palcu wrote:
Even though this was in the last C-pull, for some reason, it didn't end
up in master... Didn't see any comments on it either. Or maybe I missed
them...
In the target
Boost::thread uses functions from boost::atomic but doesn't actually
link with libboost_atomic. This works fine on platforms where
BOOST_ATOMIC_FLAG_LOCK_FREE is true but will lead to undefined
symbol references otherwise. Fix this by applying a patch from
the upstream bug tracker to add the
Signed-off-by: Valentin Popa valentin.p...@intel.com
---
.../lighttpd/{lighttpd_1.4.32.bb = lighttpd_1.4.33.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/lighttpd/{lighttpd_1.4.32.bb =
lighttpd_1.4.33.bb} (93%)
diff --git
On Thursday, November 14, 2013, Phil Blundell wrote:
Boost::thread uses functions from boost::atomic but doesn't actually
link with libboost_atomic. This works fine on platforms where
BOOST_ATOMIC_FLAG_LOCK_FREE is true but will lead to undefined
symbol references otherwise. Fix this by
On Thu, 2013-11-14 at 06:53 -0800, Khem Raj wrote:
On Thursday, November 14, 2013, Phil Blundell wrote:
Boost::thread uses functions from boost::atomic but doesn't
actually
link with libboost_atomic. This works fine on platforms where
Hi,
After upgrading oe-core and bitbake to the latest revision
(616354f13732d13c17434d5b60b166f691c25761 and
616354f13732d13c17434d5b60b166f691c25761 respectively)
I'm having broblems building my kernel.
Kernel rebuilds everytime I run bitbake some_recipe.
It starts rebuilding from do_unpack
On 11/14/2013 03:09 AM, Dominik Holland wrote:
---
meta/recipes-core/dbus/dbus.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index 5864643..0609d23 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++
On 11/14/13, 7:42 AM, Phil Blundell wrote:
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when my build
tree had the hyphen (-) in the path.
Paths with - in certainly work for me. If there are any recipes which
break in that
Yevhen Kyriukha kirgene-re5jqeeqqe8avxtiumw...@public.gmane.org
writes:
But if kernel building completed successfully then next time when I
run bitbake it starts rebuild.
My previous version of bitbake and oe-core are
565b3e31e0226c6e193ee0b031bd5e7bef25591e
and
I also changed RDEPENDS_class-native to RDEPENDS_dbus_class-native now
---
meta/recipes-core/dbus/dbus.inc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index 5864643..6612184 100644
---
On Thu, Nov 14, 2013 at 11:09 AM, Saul Wold s...@linux.intel.com wrote:
On 11/13/2013 07:08 PM, Bruce Ashfield wrote:
On Wed, Nov 13, 2013 at 8:45 PM, Otavio Salvador
ota...@ossystems.com.br wrote:
On Wed, Nov 13, 2013 at 7:54 PM, Saul Wold s...@linux.intel.com wrote:
On 11/01/2013 06:31
Updating the meta branch SRCREV to update the USB configuration:
The Beagleboard needs the USB PHY drivers in the kernel in order to enable
USB and Ethernet functionality. This fix ensures that they are built in
by tweaking the kernel config.
Tested on Beagleboard xM Rev. C2.
Updating the -rt SRCREVs to pick up the following fix:
ntp: fix ntp_notify_cmos_timer merge issue
PREEMPT_RT_FULL has a stubbed ntp_notify_cmos_timer due to a bad merge.
Renaming and restoring the full -rt functionality to this routine.
Signed-off-by: Bruce Ashfield
Richard/Saul,
Here are two 3.10 kernel updates that I've had in my tree for a
while now, and a fix from this morning for the kernel install
issues being seen on the autobuilder.
The beagleboard changes are for [YOCTO #5211] and [YOCTO #5183],
which means working USB and ethernet.
The install
On 11/13/2013 11:40 PM, qiang.c...@windriver.com wrote:
From: Qiang Chen qiang.c...@windriver.com
Commit 91c0f9e3 moves library files to base_libdir for safe while
symbol link libuuid.so and libblkid.so are placed in libdir, not
base_libdir. Thus they are missed by related develop package and
This updates lttng-modules for 2.3.3 and it also fixes the build with
3.12 Linux kernel.
While on that, we also renamed the recipe file to follow the other
lttng recipes which use the version number on it.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
On Thu, Nov 14, 2013 at 3:15 PM, Bruce Ashfield
bruce.ashfi...@gmail.com wrote:
On Thu, Nov 14, 2013 at 11:18 AM, Bruce Ashfield
bruce.ashfi...@gmail.com wrote:
On Thu, Nov 14, 2013 at 11:09 AM, Saul Wold s...@linux.intel.com wrote:
On 11/13/2013 07:08 PM, Bruce Ashfield wrote:
On Wed, Nov
On 11/14/2013 07:49 AM, Mark Hatle wrote:
On 11/14/13, 7:42 AM, Phil Blundell wrote:
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when
my build
tree had the hyphen (-) in the path.
Paths with - in certainly work for me.
On 11/14/13, 10:04 AM, Phil Blundell wrote:
On Thu, 2013-11-14 at 09:49 -0600, Mark Hatle wrote:
On 11/14/13, 7:42 AM, Phil Blundell wrote:
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when my build
tree had the hyphen (-)
ADOBE_MIRROR, HANDHELDS_CVS and E_SVN were broken links and not used by
any recipe in oe-core.
FREEDESKTOP_CVS is no longer useful because all the source code that
matters is in git; no recipe in oe-core still uses the CVS repository.
E_MIRROR, FREEBSD_MIRROR, FREESMARTPHONE_GIT still point to
On 11/14/2013 04:34 AM, Paul Woegerer wrote:
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
meta/recipes-support/liburcu/{liburcu_0.7.7.bb = liburcu_0.7.9.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/liburcu/{liburcu_0.7.7.bb =
On 11/14/2013 07:28 PM, Saul Wold wrote:
On 11/14/2013 04:34 AM, Paul Woegerer wrote:
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
meta/recipes-support/liburcu/{liburcu_0.7.7.bb = liburcu_0.7.9.bb}
| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename
On 11/14/2013 10:33 AM, Woegerer, Paul wrote:
On 11/14/2013 07:28 PM, Saul Wold wrote:
On 11/14/2013 04:34 AM, Paul Woegerer wrote:
Signed-off-by: Paul Woegerer paul_woege...@mentor.com
---
meta/recipes-support/liburcu/{liburcu_0.7.7.bb = liburcu_0.7.9.bb}
| 4 ++--
1 file changed, 2
Argh. My tools that update the SRCREVs picked up a temporary branch from
Darren and I got the wrong SRCREVs.
Use this replacement patch .. and you'll be better off :)
Bruce
On Thu, Nov 14, 2013 at 11:55 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
Updating the meta branch SRCREV to
There is an race condition where psplash is not quite exited before the unmount
occurs
causing a umount: /mnt/.psplash: target is busy message to appear, it's ok to
lazyily
unmount and not get this message
[YOCTO #5244]
Signed-off-by: Saul Wold s...@linux.intel.com
---
...
WARNING: QA Issue: Package lib32-xf86-video-vesa contains Xorg driver
(vesa_drv.so) but no xorg-abi- dependencies
WARNING: QA Issue: Package lib32-xf86-video-intel contains Xorg driver
(intel_drv.so) but no xorg-abi- dependencies
WARNING: QA Issue: Package lib32-xf86-video-omap contains Xorg
The following changes since commit ea92671d9823e3667d6ced7ac2af20f991da404d:
bitbake: cooker: replace w file opening mode with a mode (2013-11-12
17:01:37 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-xf86
On 11/14/2013 09:12 PM, Richard Purdie wrote:
On Thu, 2013-11-14 at 21:07 +0800, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
TMPDIR must be an absolute path, otherwise, the build will fail.
Special characters in TMPDIR will also cause build failures.
This patch enables
Hi All,
This cover letter contains some testing records.
Best Regards,
Chen Qi
On 11/14/2013 09:07 PM, qi.c...@windriver.com wrote:
From: Chen Qi qi.c...@windriver.com
This patch checks the validity of TMPDIR.
The TMPDIR must match the following regexp.
^/[a-zA-Z0-9\-_/.~]+$
Detailed tests
From: Chen Qi qi.c...@windriver.com
TMPDIR must be an absolute path, otherwise, the build will fail.
Special characters in TMPDIR will also cause build failures.
This patch enables checking for the validity of TMPDIR.
The logic in sanity.bbclass has also been changed a little bit. For now,
we
From: Chen Qi qi.c...@windriver.com
Changes since V1:
1. Create the directory hierarchy for TMPDIR only if TMPDIR is valid
2. Handle ABI version change only if TMPDIR has been created.
3. If we had a valid TMPDIR for last build and this time the TMPDIR hasn't
changed location, we don't check
On 11/15/2013 02:01 AM, Saul Wold wrote:
On 11/14/2013 07:49 AM, Mark Hatle wrote:
On 11/14/13, 7:42 AM, Phil Blundell wrote:
On Thu, 2013-11-14 at 06:27 -0700, Gary Thomas wrote:
Also, is - actually valid? I seem to recall having problems when
my build
tree had the hyphen (-) in the path.
Currently, the recipe which uses PACKAGES_DYNAMIC usually generates
a lot of packages which costs a lot of time on building the recipe
and do_rootfs, for example, the perl and kernel:
$ ls tmp/deploy/rpm/armv5te/perl-module-* | wc -l
621
$ ls tmp/deploy/rpm/qemux86/kernel-module-* | wc -l
268
Check whether rpcbind daemon already run before starting it.
Signed-off-by: Yue Tao yue@windriver.com
---
.../initscripts/initscripts-1.0/mountnfs.sh|9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git
The mke2fs and e2fsck commands are regular tools of e2fsprogs, so they
should be installed.
Signed-off-by: Yue Tao yue@windriver.com
---
.../recipes-devtools/e2fsprogs/e2fsprogs_1.42.8.bb |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
From: Zhong Hongbo hongbo.zh...@windriver.com
In defalut, the bluez-test script do not be installed in the rootfs.
After the user enable ptest feature, it will be install.
Signed-off-by: Zhong Hongbo hongbo.zh...@windriver.com
---
.../bluez/bluez4-4.101/install-test-script.patch | 42
From: Tobias Henkel tobias.hen...@bmw-carit.de
The icecc class often calls 'which' for determining paths. This leads
to many messages on stderr in case 'which' doesn't find the
executable. Using bb.utils.which is more appropriate here and doesn't
pollute stderr.
Signed-off-by: Tobias Henkel
60 matches
Mail list logo
