Date: Fri, 6 Nov 2015 00:24:32 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Peter Jeremy <peter@rulingia.com>, Sean Bruno <sbruno@freebsd.org>, freebsd-sparc64 <freebsd-sparc64@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Sparc64 doesn't care about you, and you shouldn't care about Sparc64 Message-ID: <20151105232431.GE31432@ivaldir.etoilebsd.net> In-Reply-To: <CAJ-VmokSfg_iuNP-MBT9VxHoxVbhGEkWtN6Oiy_ezbmhVMeteg@mail.gmail.com> References: <563A5893.1030607@freebsd.org> <20151104214451.GF47630@server.rulingia.com> <CAJ-VmokSfg_iuNP-MBT9VxHoxVbhGEkWtN6Oiy_ezbmhVMeteg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--hwvH6HDNit2nSK4j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 04, 2015 at 02:13:29PM -0800, Adrian Chadd wrote: > We don't have to expect clang support to work. Just having someone > champion the external toolchain stuff and getting sparc64 > world/kernel/release building from say, sparc64-gcc 5.x would be > enough. >=20 sparc64 has been the first arch that have been tested with external toolcha= in: build and run just fine. The problem with the external toolchain is that if you are not able to cross build the ports until you get a working toolchain available via packages, y= ou are doomed. And we do not have that Bapt --hwvH6HDNit2nSK4j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlY75S8ACgkQ8kTtMUmk6EzlqwCgvxYFG54BuIxeZy+jBM1+s+9B 8pYAoKFAHDiwulAwd3fhkNhaO3mggOxM =TPPL -----END PGP SIGNATURE----- --hwvH6HDNit2nSK4j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151105232431.GE31432>