Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-14 Thread Peter A. Bigot
On 08/14/2014 12:32 AM, Khem Raj wrote: On Wed, Aug 13, 2014 at 6:55 PM, Peter A. Bigot p...@pabigot.com wrote: EXTRA_OECONF += '${@bb.utils.contains(TUNE_FEATURES, armv7a, --with-cpu=generic-armv7-a, , d)}' Sorry a typo there you need --with-arch OK, that works. So do we need to do the

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-14 Thread Richard Purdie
On Thu, 2014-08-14 at 04:15 -0500, Peter A. Bigot wrote: What this means is that the libraries built by gcc-runtime use TARGET_CC_ARCH settings that don't necessarily match the target compiler's defaults, and that ABI conflicts can result by linking in those libraries when the non-default

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-14 Thread Peter A. Bigot
On 08/14/2014 04:40 PM, Richard Purdie wrote: On Thu, 2014-08-14 at 04:15 -0500, Peter A. Bigot wrote: What this means is that the libraries built by gcc-runtime use TARGET_CC_ARCH settings that don't necessarily match the target compiler's defaults, and that ABI conflicts can result by linking

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-14 Thread Khem Raj
On Thu, Aug 14, 2014 at 2:15 AM, Peter A. Bigot p...@pabigot.com wrote: On 08/14/2014 12:32 AM, Khem Raj wrote: On Wed, Aug 13, 2014 at 6:55 PM, Peter A. Bigot p...@pabigot.com wrote: EXTRA_OECONF += '${@bb.utils.contains(TUNE_FEATURES, armv7a, --with-cpu=generic-armv7-a, , d)}' Sorry a

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-14 Thread Khem Raj
On Thu, Aug 14, 2014 at 3:00 PM, Peter A. Bigot p...@pabigot.com wrote: I'm content with the solution in my v2 gcc patch series, but I expect someday the underlying cause will re-appear as new processors have new features with ABI impacts due to gcc target optimization. Hopefully when that

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Peter A. Bigot
On 08/11/2014 07:12 PM, Peter A. Bigot wrote: On 08/11/2014 02:02 PM, Peter A. Bigot wrote: The program below built on the target with the MACHINE=beaglebone gcc-4.9.1 compiler from Yocto/OpenEmbedded poky master produces this error: beaglebone[52]$ g++ -std=c++1y -pthread test.cc ./a.out

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Khem Raj
On Mon, Aug 11, 2014 at 12:02 PM, Peter A. Bigot p...@pabigot.com wrote: The program below built on the target with the MACHINE=beaglebone gcc-4.9.1 compiler from Yocto/OpenEmbedded poky master produces this error: beaglebone[52]$ g++ -std=c++1y -pthread test.cc ./a.out starting joining

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Peter A. Bigot
On 08/13/2014 04:18 PM, Khem Raj wrote: On Mon, Aug 11, 2014 at 12:02 PM, Peter A. Bigot p...@pabigot.com wrote: The program below built on the target with the MACHINE=beaglebone gcc-4.9.1 compiler from Yocto/OpenEmbedded poky master produces this error: beaglebone[52]$ g++ -std=c++1y -pthread

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Peter A. Bigot
On 08/13/2014 04:23 PM, Peter A. Bigot wrote: On 08/13/2014 04:18 PM, Khem Raj wrote: On Mon, Aug 11, 2014 at 12:02 PM, Peter A. Bigot p...@pabigot.com wrote: The program below built on the target with the MACHINE=beaglebone gcc-4.9.1 compiler from Yocto/OpenEmbedded poky master produces this

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Khem Raj
On Wed, Aug 13, 2014 at 2:36 PM, Peter A. Bigot p...@pabigot.com wrote: In any case, Khem can you run with this? It'd be fixed a lot better that way We do not configure target gcc with right matching cpu defaults, atomic instruction strex/ldrex are only added after armv6 but defaults for

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Peter A. Bigot
On 08/13/2014 05:05 PM, Khem Raj wrote: On Wed, Aug 13, 2014 at 2:36 PM, Peter A. Bigot p...@pabigot.com wrote: In any case, Khem can you run with this? It'd be fixed a lot better that way We do not configure target gcc with right matching cpu defaults, atomic instruction strex/ldrex are

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Khem Raj
On Wednesday, August 13, 2014, Peter A. Bigot p...@pabigot.com wrote: On 08/13/2014 05:05 PM, Khem Raj wrote: On Wed, Aug 13, 2014 at 2:36 PM, Peter A. Bigot p...@pabigot.com wrote: In any case, Khem can you run with this? It'd be fixed a lot better that way We do not configure

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Peter A. Bigot
On 08/13/2014 07:49 PM, Khem Raj wrote: On Wednesday, August 13, 2014, Peter A. Bigot p...@pabigot.com mailto:p...@pabigot.com wrote: On 08/13/2014 05:05 PM, Khem Raj wrote: On Wed, Aug 13, 2014 at 2:36 PM, Peter A. Bigot p...@pabigot.com wrote: In any

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-13 Thread Khem Raj
On Wed, Aug 13, 2014 at 6:55 PM, Peter A. Bigot p...@pabigot.com wrote: EXTRA_OECONF += '${@bb.utils.contains(TUNE_FEATURES, armv7a, --with-cpu=generic-armv7-a, , d)}' Sorry a typo there you need --with-arch OK, that works. So do we need to do the same thing for every TUNE_FEATURES

Re: [OE-core] Yocto development with C++11 threads and gcc

2014-08-11 Thread Peter A. Bigot
On 08/11/2014 02:02 PM, Peter A. Bigot wrote: The program below built on the target with the MACHINE=beaglebone gcc-4.9.1 compiler from Yocto/OpenEmbedded poky master produces this error: beaglebone[52]$ g++ -std=c++1y -pthread test.cc ./a.out starting joining pure virtual method called