Date: Thu, 5 Nov 2015 15:34:26 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Baptiste Daroussin <bapt@freebsd.org> 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: <CAJ-Vmo=kQgQMH5Fgrpgp6GZtAg4w-0tvAbeCEa%2Bweq8eu9pSsA@mail.gmail.com> In-Reply-To: <20151105232431.GE31432@ivaldir.etoilebsd.net> References: <563A5893.1030607@freebsd.org> <20151104214451.GF47630@server.rulingia.com> <CAJ-VmokSfg_iuNP-MBT9VxHoxVbhGEkWtN6Oiy_ezbmhVMeteg@mail.gmail.com> <20151105232431.GE31432@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 November 2015 at 15:24, Baptiste Daroussin <bapt@freebsd.org> wrote: > 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. >> > sparc64 has been the first arch that have been tested with external toolchain: > 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, you > are doomed. > > And we do not have that Right. You don't end up with a toolchain built if you use an external toolchain to build. I discovered this amusement when I first got this up for MIPS. :) -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=kQgQMH5Fgrpgp6GZtAg4w-0tvAbeCEa%2Bweq8eu9pSsA>