[Bug 244102] r357959/lib/clang/libllvmminimal fails buildworld with cc1plus: error: unrecognized command line option "-std=c++11"
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Feb 15 10:01:35 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244102
Mark Millard <marklmi26-fbsd at yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marklmi26-fbsd at yahoo.com
--- Comment #2 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
You are attempting to jump from the gcc 4.2.1 based environment
to well past it being supported (via a source code based
upgrade sequence). /usr/src/UPDATING has an entry:
20191226:
Clang/LLVM is now the default compiler for all powerpc architectures.
LLD is now the default linker for powerpc64. The change for powerpc64
also includes a change to the ELFv2 ABI, incompatible with the existing
ABI.
The modern toolchain requires expects that the compiler and related
toochain is llvm/clang based. Bootstrapping via source is non-trivial.
I expect that it is an old g++ 4.2.1 that is complaining about the
-std=c++11 .
See also:
https://lists.freebsd.org/pipermail/freebsd-ppc/2019-December/011042.html
Which says in part:
As of r356113 (__FreeBSD_Version 1300070) Clang is now the default
compiler for all PowerPC targets.
. . .
As mentioned before, the powerpc64 change is also a change to the new
ELFv2 ABI, which is binary incompatible with the previous ABI.
Therefore, it is recommended to perform a complete reinstall of the
system on powerpc64 platforms.
(Note: It was a bit before everything was in place.)
Trying to bootstrap via source from a g++ 4.2.1 environment is
likely not worth the effort. There are some instructions at:
https://wiki.freebsd.org/powerpc/llvm-elfv2
but it starts out saying:
Reinstalling from the latest snapshot is highly preferable to doing a source
upgrade! You have been warned!
I'm still in the middle of writing this, don't follow these instructions yet!
-- Bdragon28 2020-01-08 02:12:58
As a separate issue: head -r357549 broke powerpc64 on at least old
PowerMac G5 "Quads" and the issue was only recently identified. No fix
is checked in last I looked.
I'd target head -r357548 or somewhat before. -r357276 has a snapshot but I
do not remember its status. Later snapshots are too late. There is also
-r357530 at:
https://artifact.ci.freebsd.org/snapshot/head/r357530/powerpc/powerpc64/
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ppc
mailing list