Date: Wed, 9 Nov 2016 04:37:53 -0800 From: Mark Millard <markmi@dsl-only.net> To: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Bootstrapping a powerpc64 vs. pkg vs. base/gcc (via cross compiles) Message-ID: <B669F17A-4521-4BCC-83D4-86EF5EAEB28E@dsl-only.net>
next in thread | raw e-mail | index | archive | help
I really wish that TARGET_ARCH=3Dpowerpc64 had a tiny package repository with one item: pkg itself so that a standard bootstrap for pkg would = work. Why? A) pkg on the target needs to be built by a C/C++ compiler toolchain as things are. B) /usr/ports/base/gcc usage for getting a compiler toolchain on the = target works by putting a .txz file in place for use via pkg add = <THAT-.txz-FILE>=20 in the target environment. A similar point would go for TARGET_ARCH=3Dpowerpc . (Part of the issue is that clang/clang++ in 3.8.0 and even 3.9.0 so far is not yet appropriate for general use for powerpc64 or for powerpc, = such as incorrect code generation --and ABI violations for powerpc. FreeBSD's 3.9.0 experiment still has a couple of the llvm fixes not in place and llvm does not have everything fixed yet.) =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?B669F17A-4521-4BCC-83D4-86EF5EAEB28E>