[oe] Problem with task do_package_update_index_ipk

Hello, I've encountered a strange problem that seems to have arisen from nowhere. Essentially, when I try to bitbake an image (omap3-console-image), the process gets completely stuck in the task do_package_update_index_ipk. Its currently been running for over 4 hours. Yesterday, it was working

Re: [oe] Problem with task do_package_update_index_ipk

Hello Again, I've managed to discover what the problem was... It turns out the ipk.lock file was still present in my deploy directory, which seems to have completely messed things up. The location of the .lock file was tmp/deploy/glibc/, and when present the do_package_update_index_ipk task

[oe] [PATCH] vblade: Fix GNU_HASH QA error

From: Mike Stirling mstirl...@chipwrights.com Build fails QA with (at least) external-toolchain-csl. Fix patches makefile to pass OE's LDFLAGS to linker. Upstream-Status: Pending - issue still exists in vblade-20 Signed-off-by: Mike Stirling mstirl...@chipwrights.com ---

Re: [oe] [PATCH] gpe-mini-browser2_svn : remove fixes SRCREV

Hi Paul, On 22/07/2011, Paul Menzel paulepan...@users.sourceforge.net wrote: thank you for your patch. Thank you for the review. Please do not remove the `SRCREV` but replace it by a valid and working revision. Otherwise the builds would not be reproducible. I already wondered who added

Re: [oe] [PATCH] gpe-mini-browser2_svn : remove fixes SRCREV

On Fri, Jul 22, 2011 at 03:18:37PM +0300, Philippe De Swert wrote: Hi Paul, On 22/07/2011, Paul Menzel paulepan...@users.sourceforge.net wrote: thank you for your patch. Thank you for the review. Please do not remove the `SRCREV` but replace it by a valid and working revision.

Re: [oe] [PATCH] gpe-mini-browser2_svn : remove fixes SRCREV

Hi, Thanks for clarifying Martin. On 22/07/2011, Martin Jansa martin.ja...@gmail.com wrote: On Fri, Jul 22, 2011 at 03:18:37PM +0300, Philippe De Swert wrote: I already wondered who added one (as I originally added the svn recipe). Anyway I thought the whole idea of _svn etc were to have

Re: [oe] [PATCH] gpe-mini-browser2_svn : remove fixes SRCREV

On Fri, Jul 22, 2011 at 04:06:43PM +0300, Philippe De Swert wrote: Hi, Thanks for clarifying Martin. On 22/07/2011, Martin Jansa martin.ja...@gmail.com wrote: On Fri, Jul 22, 2011 at 03:18:37PM +0300, Philippe De Swert wrote: I already wondered who added one (as I originally added the

[oe] strange error

funny error when the OE_BASE dirname contains -OS It looks like it all occurrences in the gcc line with -OS are replaced by -O1S leading to a wrong path... | make[1]: Entering directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1' |

Re: [oe] strange error

On 07/22/2011 07:58 AM, Jaap de Jong wrote: funny error when the OE_BASE dirname contains -OS It looks like it all occurrences in the gcc line with -OS are replaced by -O1S leading to a wrong path... This is just one manifestation that seems to happen any time the build directory name

[oe] [PATCH] openembedded bitbake conf: fix for file system image creation

i've come to the insight that the tool genext2fs does a very limited job in respect to what i would consider current file system standards. it does what its name says: generating an ext2 file system. it does _not_: - generate an UUID - set the revision level to 0 (that might indicate an ext3 file

[oe] [PATCH v3]] dbus-glib-native and dbus-glib were not compiling. This patch corrects dbus-glib-native to install required files in order to let dbus-glib to compile on target.

Signed-off-by: Alessandro Sappia a.sap...@biotechware.com --- recipes/dbus/dbus-glib.inc |8 recipes/dbus/dbus-glib_0.86.bb |7 +-- 2 files changed, 5 insertions(+), 10 deletions(-) diff --git a/recipes/dbus/dbus-glib.inc b/recipes/dbus/dbus-glib.inc index

Re: [oe] [PATCH] gcc: Package libstdc++ gdb python helpers into dev package

On 06/09/2011 03:35 PM, Khem Raj wrote: People are seeing these errrors from ldconfig libstdc++.so.6.0.14-gdb.py is not an ELF file - it has the wrong magic bytes at the start. this file is moved into gdb's autoload directory if it exists there then gdb will find it when debugging and it wont