Date: Mon, 16 Jun 2014 02:13:27 -0700 From: Mark Millard <markmi@dsl-only.net> To: freebsd-ppc@freebsd.org Subject: PowerPC Packages Message-ID: <A8D49D1C-A0C9-4A3D-8EAC-330C8538B51C@dsl-only.net> In-Reply-To: <8C621F9D-6AAD-4CCC-BE2F-0EEEDC433FCB@dsl-only.net> References: <8C621F9D-6AAD-4CCC-BE2F-0EEEDC433FCB@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[Questions from someone new the the environment. So I may well be = missing some common knowledge and not have found proper reference = material yet. If so, then sorry.] libcxxrt-20131225_1.txz.out.log (as an example) reports as part of the = text for its failure... ... FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 Target: powerpc-unknown-freebsd10.0 Thread model: posix clang++: note: diagnostic msg: PLEASE submit a bug report to = http://llvm.org/bugs/ and include the crash backtrace, preprocessed = source, and associated run script. clang++: note: diagnostic msg:=20 Is clang 3.3 modern enough to be appropriate? Might 3.4 have fewer = problems (well, more old issues fixed)? Did FreeBSD 10.0 for i386 and = amd64 use 3.3? 3.4? Does (later) 9.2-STABLE through 9.3-BETA3 for = powerpc and/or powerpc64 include clang 3.4? 3.3? (I think it is clang = 3.4 for (later) 9.2-STABLE through 9.3-BETA3 for powerpc/powerpc64 but = for now I'm away from the powermacs that I would use to check.) =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8D49D1C-A0C9-4A3D-8EAC-330C8538B51C>