Re: [oe] llvm fails to build

On Wed, May 2, 2012 at 11:33 PM, Jaap de Jong wrote: > Hi all, > > trying to compile openjdk-6, it fails with: > > | > /media/OpenEmbedded/oe-core/build/tmp-angstrom_2010_x-eglibc/work/armv5te-angstrom-linux-gnueabi/llvm2.8-2.8-r0/llvm-2.8/lib/ExecutionEngine/JIT/Intercept.cpp: > In constructor '{

Re: [oe] Openembedded and ld-linux-armhf.so.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 03-05-12 08:48, Martin Ertsås schreef: > On 05/02/12 23:06, Khem Raj wrote: >> On 05/02/2012 02:35 AM, Martin Ertsås wrote: >>> The patches posted seems to be working fine. I at least didn't have >>> any problems with them. >> >> >> thanks for tr

Re: [oe] Openembedded and ld-linux-armhf.so.3

On 05/03/12 09:48, Koen Kooi wrote: > Op 03-05-12 08:48, Martin Ertsås schreef: > > On 05/02/12 23:06, Khem Raj wrote: > >> On 05/02/2012 02:35 AM, Martin Ertsås wrote: > >>> The patches posted seems to be working fine. I at least didn't have > >>> any problems with them. > >> > >> > >> thanks for

[oe] yocto 1.2: 2nd experiences: image building problems

Dear all, I'm migrating a project from oe-classic to yocto 1.2. This goes fairly smoothly. Got some warnings I reported before. If I build my app it runs fine (with the uclibc from oe-classic that is already on the board). Next step was to try to build a complete image. There I encountered two i

Re: [oe] llvm fails to build

Thanks! That helps a lot!! Unfortunately I'm not familiar with submitting the patch... (shame on me! You may sent me a link for the howto) However this is the patch I used diff --git a/llvm-2.8/lib/ExecutionEngine/JIT/Intercept.cpp b/llvm-2.8/lib/ExecutionEngine/JIT/Intercept.cpp index

Re: [oe] [meta-kde] Test images (was: Re: [OE-core] RFC: Porting KDE Plasma Active (WIP))

2012/5/2 Koen Kooi : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Op 23-04-12 15:49, Samuel Stirtzel schreef: >> 2012/4/23 Koen Kooi : >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >>> Op 23-04-12 09:17, Samuel Stirtzel schreef: 2012/4/20 Koen Kooi : >>> And do you have a

Re: [oe] [meta-oe 1/1] lxc : Add recipe for building Linux Containers tools.

On 05/02/2012 02:54 PM, Koen Kooi wrote: > Op 02-05-12 19:45, Philip Balister schreef: >> Linux containers are a lightweight virtualization system. > >> Compile tested on F15 and lightly run tested on a pandaboard. > >> Signed-off-by: Philip Balister --- >> meta-oe/recipes-extended/lxc/lxc_git.

[oe] upgrading from oe-classic to oe-core

Hi All, If I have devices running on oe-classic and I want to upgrade them to oe-core, will the upgrade be without worries? It will probably download all packages? Or do I have to takes special steps? Thanks, Jaap ___ Openembedded-devel mailing list

Re: [oe] upgrading from oe-classic to oe-core

Op 3 mei 2012 13:29 heeft Jaap de Jong het volgende geschreven: > Hi All, > If I have devices running on oe-classic and I want to upgrade them to > oe-core, will the upgrade be without worries? > It will probably download all packages? > Or do I have to takes special steps? Depends on the devices

Re: [oe] upgrading from oe-classic to oe-core

On 05/03/2012 01:40 PM, Frans Meulenbroeks wrote: Op 3 mei 2012 13:29 heeft Jaap de Jong het volgende geschreven: Hi All, If I have devices running on oe-classic and I want to upgrade them to oe-core, will the upgrade be without worries? It will probably download all packages? Or do I have to

[oe] how to rebuild packages

Probably a total stupid question... In oe-classic I used to use bitbake -c clean packageX bitbake packageX This does not seem to work on oe-core. Even removing the directory build/tmp-angstrom_2010_x-eglibc/work/armv5te-angstrom-linux-gnueabi/packageX* does not help... What is the way

Re: [oe] how to rebuild packages

On Thu, May 03, 2012 at 03:27:39PM +0200, Jaap de Jong wrote: > Probably a total stupid question... > > In oe-classic I used to use > > bitbake -c clean packageX > bitbake packageX > > This does not seem to work on oe-core. > Even removing the directory > build/tmp-angstrom_2010_x-egl

Re: [oe] upgrading from oe-classic to oe-core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 03-05-12 14:29, Jaap de Jong schreef: > > > On 05/03/2012 01:40 PM, Frans Meulenbroeks wrote: >> Op 3 mei 2012 13:29 heeft Jaap de Jong het >> volgende geschreven: >>> Hi All, If I have devices running on oe-classic and I want to upgrade >>> the

[oe] [2011.03-maintenance 0/1] pull request 20120503

Hi Tom, please pull this commit into 2011.03-maintenance branch. It fixes a build problem with icedtea6-native and newer glibc versions. The fix is well tested in our own environment. Thx, Steffen The following changes since commit 21613e405cad072feef779c8e9b374a2f0984158: docbook-utils-nativ

[oe] [2011.03-maintenance 1/1] icedtea6-native-1.7.10: backport S7103224

Backport the fix for 7103224. This fix allows icedtea6 to be built with (very) new glibc versions. It was originally suggested by Omair Majid from RedHat. For details see:

Re: [oe] Openembedded and ld-linux-armhf.so.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/03/2012 12:51 AM, Martin Ertsås wrote: > Fair point, I was just told that some packages might look at the > name of the toolchain, and perhaps not give the optimal path for > hard floats with the name of linux-gnueabi. Clearly some packages > do

Re: [oe] right directory for a recipe

Hi Rado, Il giorno 02/mag/2012, alle ore 22:06, Radoslav Kolev ha scritto: > On Tue, May 1, 2012 at 10:10 PM, Andrea Galbusera wrote: >> What would be the right directory to put libmodbus in? I understand >> recipes-* names are somewhat self explanatory, but I'm still confused >> if "recipes-e

Re: [oe] [yocto] yocto 1.2: 2nd experiences: image building problems

On 05/03/2012 01:01 AM, Frans Meulenbroeks wrote: Dear all, I'm migrating a project from oe-classic to yocto 1.2. This goes fairly smoothly. Got some warnings I reported before. If I build my app it runs fine (with the uclibc from oe-classic that is already on the board). Next step was to try t