Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-18 Thread Thilo Fromm
Hello Khem, Actually we'd like to stay on HEAD and build our own distribution on top of that. Hence I'm more interested in getting ti81xx-psp-2.6.37 to work with gcc-4.7. I'll try Martin Jansa's hint (-mno-unaligned-access) next. then use the default gcc that angstrom head is using which is

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello *.*, Khem Raj (3):      eglibc-2.12: Remove      binutils-2.20: Remove      gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these (linux-ti81xx-psp_2.6.37). Unfortunately gcc = 4.6

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Gary Thomas
On 2012-05-16 04:50, Thilo Fromm wrote: Hello *.*, Khem Raj (3): eglibc-2.12: Remove binutils-2.20: Remove gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello Gary, Hello *.*, Khem Raj (3):      eglibc-2.12: Remove      binutils-2.20: Remove      gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these (linux-ti81xx-psp_2.6.37).

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Martin Jansa
On Wed, May 16, 2012 at 12:50 PM, Thilo Fromm fr...@dresearch-fe.de wrote: Hello *.*, Khem Raj (3):      eglibc-2.12: Remove      binutils-2.20: Remove      gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello Martin, Hello *.*, Khem Raj (3):      eglibc-2.12: Remove      binutils-2.20: Remove      gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these (linux-ti81xx-psp_2.6.37).

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello Gary, Khem Raj (3):      eglibc-2.12: Remove      binutils-2.20: Remove      gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these (linux-ti81xx-psp_2.6.37). Unfortunately gcc=

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Gary Thomas
On 2012-05-16 06:41, Thilo Fromm wrote: Hello Gary, Khem Raj (3): eglibc-2.12: Remove binutils-2.20: Remove gcc-4.5: Remove Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. You only get a heavily patched 2.6.37 kernel from TI for these

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello Gary, [ ti81xx-psp-2.6.37 defconfig ] The only real differences (modulo the hardware/peripherals in use) are some of the kernel debugging settings.  Perhaps they are causing some problems with the newer compiler.  The diffs between our configurations are attached. Thanks, but I don't

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Khem Raj
On Wed, May 16, 2012 at 3:50 AM, Thilo Fromm fr...@dresearch-fe.de wrote: Removing gcc-4.5 would kill Texas Instruments DaVinci (dm814x, dm816x) support. how so ? can you stick with denzil stable branch if you so heavily depend on 4.5 and meanwhile let the software stack for these SOCs ported

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Khem Raj
On Wed, May 16, 2012 at 8:03 AM, Thilo Fromm fr...@dresearch-fe.de wrote: Thanks, looks like I'll need it :)  By the way, we successfully pulled gcc-4.5 in our layer and are building with gcc-4.5 on angstrom-v2012.x right now. Since you're on 8148 as well, and in case you would like to stay

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Thilo Fromm
Hello Khem, Thanks, looks like I'll need it :)  By the way, we successfully pulled gcc-4.5 in our layer and are building with gcc-4.5 on angstrom-v2012.x right now. Since you're on 8148 as well, and in case you would like to stay up-to-date on what we're doing, just check

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-16 Thread Khem Raj
On Wed, May 16, 2012 at 9:47 AM, Thilo Fromm fr...@dresearch-fe.de wrote: Actually we'd like to stay on HEAD and build our own distribution on top of that. Hence I'm more interested in getting ti81xx-psp-2.6.37 to work with gcc-4.7. I'll try Martin Jansa's hint (-mno-unaligned-access) next.

[oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-15 Thread Khem Raj
Hi Koen Since meta-oe is not branched for denzil this patch removes the old components in there for toolchain recipes. I have left gcc 4.6 in there for now since OE-Core still have those recipes. The following changes since commit 14869e500c1a2f6be4704bf7399435fda00dc34c: klibc: upgrade to

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-15 Thread Denys Dmytriyenko
On Tue, May 15, 2012 at 03:01:42PM -0700, Khem Raj wrote: Hi Koen Since meta-oe is not branched for denzil this patch removes the old Did you mean is now branched above? Since 4.6/4.7 is now seems to work fine for me: Acked-by: Denys Dmytriyenko de...@ti.com components in there for

Re: [oe] [toolchain-layer][pull-request] Remove old toolchain recipes

2012-05-15 Thread Khem Raj
On Tuesday, May 15, 2012, Denys Dmytriyenko de...@denix.org wrote: On Tue, May 15, 2012 at 03:01:42PM -0700, Khem Raj wrote: Hi Koen Since meta-oe is not branched for denzil this patch removes the old Did you mean is now branched above? Yes indeed it was a typo Since 4.6/4.7 is now seems