Basic context for the observation (powerpc64 example):
# freebsd-version -ku; uname -a
11.0-CURRENT
11.0-CURRENT
FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11
19:23:14 PDT 2015
root@FBSDG4C0:/usr/obj/powerpc.powerpc64/usr/srcC/sys/GENERIC64vtsc-NODEBUG
powerpc
Basic context for the observation (powerpc64 example):
# freebsd-version -ku; uname -a
11.0-CURRENT
11.0-CURRENT
FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11
19:23:14 PDT 2015
root@FBSDG4C0:/usr/obj/powerpc.powerpc64/usr/srcC/sys/GENERIC64vtsc-NODEBUG
powerpc
Nathan W. wrote:
This is not the right one. That is related to clang 3.4. The issue is
that clang 3.5+ require a C++11 compiler to build. ...
The text that I quoted is from the 11.0-CURRENT UPDATING entry that starts with
the non-FreeBSD-variant-specific 3.5.0 background information below.
This is not the right one. That is related to clang 3.4. The issue is
that clang 3.5+ require a C++11 compiler to build. GCC 4.2 is not a
C++11 compiler and so the clang build was disabled. This makes the
upgrade path when clang becomes the default compiler a little bumpy, but
that did not
Well there is an entry but when I read it I did not find it clear about the
10.x status.
I think the implication is that the 9.x paragraph also applies to 10.x:
On 9.x [and 10.x] installations where clang is enabled by default, e.g.
on x86 and
powerpc, libc++ will not be
On Mar 12, 2015, at 6:36 PM, Mark Millard mar...@dsl-only.net wrote:
Basic context for the observation (powerpc64 example):
# freebsd-version -ku; uname -a
11.0-CURRENT
11.0-CURRENT
FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11
19:23:14 PDT 2015
