This fixes a problem found on the AB when sstate from one machine
is used on by another machine.
Added test for file existense.
Sau!
The following changes since commit 368b150416688654e35229a63b87177b52e83d02:
populate_sdk_rpm: add pkgconfig(pkg-config) to the list (2011-09-23 19:55:43
+0100
Added a native sstate post install function to fix the links
created between /lib and /usr/lib for the library files. These
links could point to an invalid build area when using shared state.
Signed-off-by: Saul Wold
---
meta/recipes-support/attr/acl_2.2.51.bb |2 +-
meta/recipes-support/at
If we build say gnome based image on a build system which does not have
gnome e.g. kubuntu then packages like gedit do not build since it uses
gnome files from host system which are non existent on kubuntu
Signed-off-by: Khem Raj
---
.../gnome-doc-utils/sysrooted-pkg-config.patch | 37
Richard,
This fixes a problem found on the AB when sstate from one machine
is used on by another machine.
Sau!
The following changes since commit 368b150416688654e35229a63b87177b52e83d02:
populate_sdk_rpm: add pkgconfig(pkg-config) to the list (2011-09-23 19:55:43
+0100)
are available in t
Added a native sstate post install function to fix the links
created between /lib and /usr/lib for the library files. These
links could point to an invalid build area when using shared state.
Signed-off-by: Saul Wold
---
meta/recipes-support/attr/acl_2.2.51.bb |2 +-
meta/recipes-support/at
On Fri, Sep 23, 2011 at 16:46, Dmitry Eremin-Solenikov
wrote:
...
> +FILES_${PN} = "${libdir}/lib*.so.* \
> + ${sysconfdir}/bash_completion.d/dbus-bash-completion.sh \
> + ${libexecdir}/dbus-bash-completion-helper"
...
I'd prefer to have this in another package.
--
Ot
As per gcc PR 11147, libffi installs headers into a target dependent
place (/usr/lib/). Include a rule to include those files into
libffi-dev package.
Reference: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11147
Signed-off-by: Dmitry Eremin-Solenikov
---
meta/recipes-gnome/libffi/libffi_3.0
From: lumag
First, this lib is usefull for coverage analysis-enabled building.
Second, this fixes the warning about unpackaged files in libgcc recipe.
Signed-off-by: Dmitry Eremin-Solenikov
Signed-off-by: Koen Kooi
Signed-off-by: Dmitry Eremin-Solenikov
---
meta/recipes-devtools/gcc/gcc-4.5.
Behave more like plain gconf: include a dtd and .la files into -dev
package.
Signed-off-by: Dmitry Eremin-Solenikov
---
meta/recipes-gnome/gnome/gconf-dbus_705.bb |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-gnome/gnome/gconf-dbus_705.bb
b/meta/recipe
Signed-off-by: Dmitry Eremin-Solenikov
---
meta/recipes-core/dbus/dbus-glib.inc |4 +++-
meta/recipes-core/dbus/dbus-glib_0.92.bb |2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus-glib.inc
b/meta/recipes-core/dbus/dbus-glib.inc
index 70
There is no point in downloading a tarball with no clear upstream (other than
icecc itself) and then patching it. Rather put new script in the source tree.
Signed-off-by: Dmitry Eremin-Solenikov
---
.../icecc-create-env-native/icecc-create-env | 192
.../icecc-create-
Long time ago a066e7ca90a28d5681c5fa895a29e999ed7c88b was committed to
address possible problems with compilation of nscd during
eglibc-nativesdk build. Problems were related to the way gcc searches
for headers to check if it should enable it's own stack smash protection
bits or it can relay on egl
eglibc.inc contains packaging rules that depend on PKGSUFFIX expansion.
However that variable wasn't expanded properly in some case. E.g.
PACKAGES = " ... nscd${PKGSUFFIX} ..."
FILES_nscd${PKGSUFFIX} = "${sbindir}/nscd*"
would be expanded to
PACKAGES = " ... nscd-nativesdk ..."
FILES_nscd = "${s
Add a bash-completion recipe. Largely based on the one from oe-dev repo.
Changes:
1) Version bump to most recent bash-completion upstream tarball
2) Dropped custom profile.d script in favour of upstream one.
Signed-off-by: Dmitry Eremin-Solenikov
---
.../bash-completion/bash-completion_20060301.
Currently if I build packages for several targets (e.g. for armv5te tosa
and for armv7a beagleboard) oe will use single ccache dir for both of
those targets: build/ccache/arm-oe-linux-gnueabi. However those targets
use different opcodes, different features and binaries created for one
of those targ
Signed-off-by: Dmitry Eremin-Solenikov
---
meta/conf/distro/include/default-providers.inc |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta/conf/distro/include/default-providers.inc
b/meta/conf/distro/include/default-providers.inc
index d51ac64..6e281cc 100644
--- a/m
On Fri, Sep 23, 2011 at 14:30, Richard Purdie
wrote:
...
> I don't really see the point of this. Basically you're asking that every
> time there is a commit to the branch there is also a merge commit. You
> can just as easily either force a checkout of master, or merge against
> master with a one
On Fri, 2011-09-23 at 13:41 -0300, Otavio Salvador wrote:
> On Thu, Sep 22, 2011 at 20:33, Richard Purdie
> wrote:
> > On Thu, 2011-09-22 at 09:49 -0300, Otavio Salvador wrote:
> >> I noticed the 2011-1 branch today and it seems it is not fully merged
> >> into master; this is a mistake since it w
On Thu, Sep 22, 2011 at 20:33, Richard Purdie
wrote:
> On Thu, 2011-09-22 at 09:49 -0300, Otavio Salvador wrote:
>> I noticed the 2011-1 branch today and it seems it is not fully merged
>> into master; this is a mistake since it will create an upgrade path
>> problem for users of it.
>
> Its a bra
On 09/22/2011 04:04 PM, Martin Jansa wrote:
Hi,
after this patch PKGSUFFIX is probably evaluated too late and this:
# PREFERRED_PROVIDER_glibc-thread-db=eglibc-thread-db
PREFERRED_PROVIDER_glibc-thread-db="eglibc-thread-db"
# RPROVIDES_eglibc-thread-db${PKGSUFFIX}=glibc-thread-db${PKGSUFFIX}
RP
This patch is indented to add new functionality,
specifically, the patch adds support for
the QtMobility 1.2 package.
Added two recipes:
1) qt-mobility-x11 builds the QtMobility 1.2 package
on the basis of qt4-x11-free;
2) qt-mobility-embedded builds the QtMobility 1.2 package
on the basis o
21 matches
Mail list logo
