C++ buildproblems with arm-none-eabi-g++ v6 about release-specs HOT 15 CLOSED

@OlegHahm I can compile the cpp11_condition_variable test without issues for the samr21-xpro using compiler version 5.4.1. However, my stdlib.h file has a different location:

$ find . -name "stdlib.h"
arm-none-eabi/include/c++/5.4.1/tr1/stdlib.h
arm-none-eabi/include/machine/stdlib.h
arm-none-eabi/include/stdlib.h

Where did you get the 6.2.0 version?

From the Arch repository:

community/arm-none-eabi-gcc 6.2.0-1 [installed]
    The GNU Compiler Collection - cross compiler for ARM EABI (bare-metal) target

/usr/arm-none-eabi/include/stdlib.h
/usr/arm-none-eabi/include/c++/6.2.0/stdlib.h
/usr/arm-none-eabi/include/c++/6.2.0/tr1/stdlib.h
/usr/arm-none-eabi/include/machine/stdlib.h

from release-specs.

I ran that test yesterday with success. Here my compiler:

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.2.1 20151202 (release) [ARM/embedded-5-branch revision 231848]

from release-specs.

Works with version 5.4 as well. Can't find version 6 for macOS. Could that be a compiler bug?

from release-specs.

Maybe @gebart has the right compiler and can reproduce this?

from release-specs.

From GNU ARM Embedded Toolchain:

6.0 series is the current focus of development.

Maybe it's advisable to use a stable toolchain for RIOT development. ;)

from release-specs.

Why do you conclude that 6.2 is not stable?

from release-specs.

And why got this issue renamed?

from release-specs.

And why got this issue renamed?

I'm not aware of renaming the issue. Sorry, if I did it by accident.

from release-specs.

I renamed it. I did not think " 01-tests/task 01 Release 2016.10 - RC1" was really helpful

a) because it did not describe the problem
b) because task 1.1 has nothing to do with arm-none-eabi-g++ (since those are about native)

from release-specs.

@OlegHahm I can reproduce on arch with

arm-none-eabi-g++ (Arch Repository) 6.2.0

from release-specs.

btw, its also failing for me on native, with:

RIOT/sys/cpp11-compat/condition_variable.cpp: In member function ‘void riot::condition_variable::wait(riot::unique_lock<riot::mutex>&)’:
RIOT/sys/cpp11-compat/condition_variable.cpp:84:26: error: throw will always call terminate() [-Werror=terminate]
       "Mutex not locked.");

from release-specs.

@cgundogan Are you using gcc 6.something on native as well?

from release-specs.

@josephnoir g++ (GCC) 6.2.1 20160830

from release-specs.

@josephnoir I also hit that error with arm-none-eabi-g++, so it's not just native.

from release-specs.

Confirmed.

from release-specs.