In file included from src/gcc/gcc/auto-profile.c:25:
In file included from /usr/include/c++/v1/map:446:
/usr/include/c++/v1/functional:1398:2: error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean simply 'fancy_abort'?
/usr/include/c++/v1/__config:390:15: note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
src/gcc/gcc/system.h:700:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
regressed by: https://github.com/llvm-mirror/libcxx/commit/14c09a2413ed
Looks like bug 212465 except I don't understand why Dimitry claims it's specific to libc++ 3.9 when the port builds fine on /head at the moment.
Ah, it was a typo.
I'm afraid, it is build environment unsupported by vendor…
I've updated port to latest release, which is 6.2.1. I'm not sure, is it still affected by this problem, as one of related bugs says "Newer gcc ports, such as gcc5 and gcc6 don't show this issue".
(In reply to Lev A. Serebryakov from comment #4)
> I've updated port to latest release, which is 6.2.1. I'm not sure, is it
> still affected by this problem, as one of related bugs says "Newer gcc
> ports, such as gcc5 and gcc6 don't show this issue".
For gcc5 this is still an issue (see bug 216266), but for gcc6 it has been solved in a different way by upstream:
E.g. they now include any required C++ headers in gcc/system.h when INCLUDE_LIST, INCLUDE_MAP, etc are defined.
I confirm, gcc-arm-embedded-6.2.20161216 built fine with clang/libc++ 4.0.