Date: Thu, 10 Nov 2016 23:10:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214405] base/gcc: -424540 for TARGET_ARCH=powerpc64 example: g++ does not find the standard c++ headers (file placement vs. lookup mismatches) Message-ID: <bug-214405-13-Wpj4NgHoSP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214405-13@https.bugs.freebsd.org/bugzilla/> References: <bug-214405-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214405 --- Comment #1 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #0) I have not placed symbolic links (or hard links) for the stand C++ headers = (and their supporting headers) and so have no workaround in place for this issue. So my testing of base/gcc (and base/binutils) stopped with this for now. I will note that the little bit of attempted use of base/gcc had issues that I'd not fully tracked down. For example gettext-runtime's build classified libasprintf as not to be built when cc and c++ pointed to the base/gcc compilers. (That in turn lead to gettext-runtime failing to finish its install.) [Switching cc and c++ back to clang and clang++ did not have this problem. = Note that I've been one of the folks experimenting with finding powerpc64 and powerpc clang/clang++ targeting problem details for submittal to llvm and so use them despite their not being ready for general use for those targets ye= t. This switch is not an option for most folks.] --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214405-13-Wpj4NgHoSP>