Updating the META SRCREV to pickup these commits:
59f350e meta: Add common-pc-tiny.scc
0996ca9 tiny: Minimize the tiny config
d6b57bb meta: common-pc add dependencies to cfg
Which update the configuration for the tiny profile of the kernel
for the 3.2 release.
cc: Darren Hart
Signed-off-b
Richard/Saul,
Here's an update of the tiny kernel configuration for 3.2. Darren
and I have both tested this, and there's no impact on existing
configurations (outside of minor tweaks to common-pc), so there's
little risk in this pull request.
Cheers,
Bruce
The following changes since commit 869
Hi Martin,
The fixes have been merged into oe-core, and it changed a lot.
// Robert
On 03/27/2012 11:19 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 09:49:36PM +0800, Robert Yang wrote:
On 03/27/2012 09:35 PM, Martin Jansa wrote:
On Tue, Mar 27, 2012 at 09:28:09PM +0800, Robert Yang wr
From: Zhai Edwin
All,
Previous version of nVidia GLX driver in Ubuntu 10 cause qemu segfault, so we
fall back to Mesa GLX driver if detecting nVidia driver installed. From Ubuntu
11, nVidia GLX driver works well, while previous work around cause GL apps
failure. So this work around is limited in
From: Zhai Edwin
Previous version of nVidia GLX driver in Ubuntu 10 cause qemu segfault, so we
fall back to Mesa GLX driver if detecting nVidia driver installed. From Ubuntu
11, nVidia GLX driver works well, while previous work around cause GL apps
failure. So this work around is limited in Ubunt
On 04/01/2012 08:47 AM, Paul Eggleton wrote:
On Thursday 02 February 2012 12:50:16 Samuel Stirtzel wrote:
There are other CMake configure pitfalls (all cross compiling scripts
in kdelibs are commented out) but it seems that at least the most of
them showed already during build time.
Unfortun
On Thursday 02 February 2012 12:50:16 Samuel Stirtzel wrote:
> There are other CMake configure pitfalls (all cross compiling scripts
> in kdelibs are commented out) but it seems that at least the most of
> them showed already during build time.
Unfortunately when I tried to build kdelibs4 I got th
On Sun, 1 Apr 2012, Paul Eggleton wrote:
> On Saturday 31 March 2012 19:12:12 Robert P. J. Day wrote:
> > the bitbake manual lists "fakeroot" as a possible variable flag,
> > along with things like "nostamp", "noexec" and so on. but i don't see
> > fakeroot being used as a flag anywhere in the
On Saturday 31 March 2012 19:12:12 Robert P. J. Day wrote:
> the bitbake manual lists "fakeroot" as a possible variable flag,
> along with things like "nostamp", "noexec" and so on. but i don't see
> fakeroot being used as a flag anywhere in the source tree. has that
> changed?
No, fakeroot is
the bitbake manual lists "fakeroot" as a possible variable flag,
along with things like "nostamp", "noexec" and so on. but i don't see
fakeroot being used as a flag anywhere in the source tree. has that
changed?
rday
--
==
There are various conditions that lead to duplicate entries in the dot graph
which need to get fixed, but this patch is a catchall. A previous attempt to
address this only works on rpm which gives a \n seperated output, opkg doesn't.
Another benefit is that the sort order is now know, leading to
When nothing has changed an empty commit prefixed with "No changes" will get
generated so that the commit log of the buildhistory repo provides a complete
log of all builds performed, not just those that resulted in changes.
Signed-off-by: Koen Kooi
---
meta/classes/buildhistory.bbclass |2
This seperates out image changes from package changes making the image diffs a
lot easier to read.
Signed-off-by: Koen Kooi
---
meta/classes/buildhistory.bbclass |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/meta/classes/buildhistory.bbclass
b/meta/classes/buildh
another sort of "best practices" question while trying to dispel
some confusion. in bitbake.conf, we have:
IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
fair enough, but since this is in bitbake.conf, it clearly(?)
represents delayed processing since this is being defined before the
target task
C getpid needs unistd.h for getting
its signature
Signed-off-by: Khem Raj
---
meta/recipes-qt/qt4/files/gcc-scope.patch | 48 +
meta/recipes-qt/qt4/qt-mobility_1.2.0.inc |6 ++-
2 files changed, 52 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-q
On Sat, 2012-03-31 at 14:49 +0800, Lianhao Lu wrote:
> This patch serie fixed bunch of things for nativesdk recipes, including:
>
> 1. Fixed the issue of reading in incorrect pkgdata files of
> do_package_write_xxx.
> 2. Avoided crosssdk tasks generating different task hashs for different
> MACH
On Fri, 2012-03-30 at 15:28 -0700, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> This Fixes bug: [YOCTO #2176]
>
> This fixes the following issue as mentioned in the bug:
> If nasm-native has to be rebuilt (due to a signature change) it will fail:
>
> | checking for a BSD-compatibl
On Fri, 2012-03-30 at 15:28 -0700, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> This makes the libraries located in places like this findable:
> /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib
>
> Which avoids linking cross canadian sdk executables with host libraries
On Fri, 2012-03-30 at 20:17 -0400, Robert P. J. Day wrote:
> goofing around with "bitbake -e" and, with a clean oe-core checkout,
> both of the following work:
>
> $ bitbake -e
> $ bitbake -e core-image-core
>
> now, just for fun, i added a trivial recipe file to that images/
> directory to see
On Sat, 2012-03-31 at 08:59 -0700, Steve Sakoman wrote:
> On Sat, Mar 31, 2012 at 8:34 AM, Richard Purdie
> wrote:
>
> > Hmm, yes. We already have a bug open against git but I'd like to
> > understand shadow-native and sqlite. If you have the failure logs for
> > those two, I think it would be wo
On Sat, Mar 31, 2012 at 8:34 AM, Richard Purdie
wrote:
> Hmm, yes. We already have a bug open against git but I'd like to
> understand shadow-native and sqlite. If you have the failure logs for
> those two, I think it would be worth opening bugs for them.
Details for shadow-native and sqlite bel
On Tuesday 27 March 2012 12:50:07 Paul Eggleton wrote:
> Andreas, if you could review these that would be much appreciated.
>
>
> The following changes since commit 644b7503c37fd73730dd3d7841463b158b8934ed:
>
> guile: Deal with hardcoded path issues (2012-03-27 00:28:41 +0100)
>
> are availab
On Sat, 2012-03-31 at 08:04 -0700, Steve Sakoman wrote:
> On Sat, Mar 31, 2012 at 7:07 AM, Richard Purdie
> wrote:
> > As some people have noticed, there are some rebuild issues happening due
> > to sstate and the use of hashes in the stamp files. By this I mean the
> > case where due to some chec
On Sat, Mar 31, 2012 at 7:07 AM, Richard Purdie
wrote:
> As some people have noticed, there are some rebuild issues happening due
> to sstate and the use of hashes in the stamp files. By this I mean the
> case where due to some checksum change, some task gets rerun and the
> task was not written t
On Sat, Mar 31, 2012 at 7:39 AM, Khem Raj wrote:
> nptl is bogus now a days. so please delete it completely.
heh I must have said in GLIBC_ADDON context its bogus. Since its _the_
only thread implementation in eglibc/glibc
___
Openembedded-core mailing
On Fri, Mar 30, 2012 at 11:49 PM, Lianhao Lu wrote:
>
> GLIBC_ADDONS ?= "ports,nptl,libidn"
> +GLIBC_ADDONS_virtclass-nativesdk = "nptl"
nptl is bogus now a days. so please delete it completely.
___
Openembedded-core mailing list
Openembedded-core@lis
On Sat, 2012-03-31 at 14:49 +0800, Lianhao Lu wrote:
> Set only necessary GCC_ADDONS for eglibc-nativesdk so that it is not
> dependant on the target eglibc's GCC_ADDONS settings.
You mean GLIBC_ADDONS, right? :)
> Signed-off-by: Lianhao Lu
> ---
> meta/recipes-core/eglibc/eglibc_2.13.bb |3
As some people have noticed, there are some rebuild issues happening due
to sstate and the use of hashes in the stamp files. By this I mean the
case where due to some checksum change, some task gets rerun and the
task was not written to run a second time.
In other words all tasks are not idempoten
28 matches
Mail list logo
