Basic context (more context details listed later):
# freebsd-version -ku; uname -ap
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
Which compiler are you building with? Just using the normal lang/gcc
works for me without issue doing make install in lang/clang36. Are you
sure you don't have any local diffs or stale files?
-Nathan
On 03/16/15 17:18, Mark Millard wrote:
Basic context (more context details listed later):
#
Basic context (more context details listed later):
# freebsd-version -ku; uname -ap
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
I tried portmaster -tDK --no-confirm lang/clang36 on a powerpc (non-64):
$ freebsd-version -ku ; uname -ap
11.0-CURRENT
11.0-CURRENT
FreeBSD FBSDG4C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Mon Mar 9
22:24:27 PDT 2015 root@FBSDG4S0:/usr/obj/usr/srcC/sys/GENERICvtsc-NODEBUG
powerpc
Basic context (more is listed later):
# freebsd-version -ku ; uname -ap
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 powerpc64
I agree that my experiment is not what should be the 11.0-CURRENT official file
contents by any means: it would break other contexts/uses for sure.
But I expect it was appropriate to identify one thing that contributes to the
observed behavior of cc1plus reporting -std=c++11 as unrecognized.
On Mar 16, 2015, at 7:02 PM, Dimitry Andric d...@freebsd.org wrote:
On 16 Mar 2015, at 09:02, Mark Millard mar...@dsl-only.net wrote:
I found why gcc 4.2.1's cc1plus was getting -std=c++11 for the
CROSS_TOOLCHAIN=powerpc64-gcc compiles that involve WITH_CLANG= .
(WITHOUT_CLANG= does
On 2015-Mar-16, at 07:41 AM, Ryan Stone ryst...@gmail.com wrote:
This should have been fixed in r276760:
https://svnweb.freebsd.org/changeset/base/279760
Ahh. Thanks.
I'm at -r279514 because when I tried to get from there to -r279813 for my
powerpc64/powerpc context it was a disaster.
This should have been fixed in r276760:
https://svnweb.freebsd.org/changeset/base/279760
___
freebsd-toolchain@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to
The last powerpc (non-64) build test to complete ran where only built-in-world
compilers originally existed (gcc 4.2.1 and clang 3.4.1 this time. For this
context portmaster -tDK --no-confirm lang/clang36 initiated installing
lang/gcc (i.e., 4.8.4 at this point) in order to provide itself with
10 matches
Mail list logo