Date: Tue, 11 Aug 2015 11:02:03 -0700 From: John Baldwin <jhb@freebsd.org> To: Baptiste Daroussin <bapt@freebsd.org> Cc: Adrian Chadd <adrian.chadd@gmail.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Bill Sorenson <instructionset@gmail.com> Subject: Re: Sparc64 support Message-ID: <3293168.mJnTOSukKj@ralph.baldwin.cx> In-Reply-To: <20150808015610.GL43782@ivaldir.etoilebsd.net> References: <CACcTwYmS1c5uoO-WiJQDwgqYAevX7WZ7ZrP297hnOu7cNET3CA@mail.gmail.com> <CAJ-VmomyKJaVhBR5=Dny%2BUpKoV6wmJJGNR6UKgjWq0UBRz=sMQ@mail.gmail.com> <20150808015610.GL43782@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, August 08, 2015 03:56:10 AM Baptiste Daroussin wrote: > On Fri, Aug 07, 2015 at 04:54:46PM -0700, Adrian Chadd wrote: > > Hi, > > > > I've tested it with mips/mips64. It works out mostly okay. There are > > still rough edges, because in the mips world we have different > > defaults in our base system gcc to what the current toolchain expects. > > But at least for mips/mips64 it spits out a kernel and binaries that > > work. > > > > What I did to make the MIPS bits call the external toolchain: > > > > make <existing options> NO_WERROR=1 CROSS_TOOLCHAIN=mips-gcc buildworld > > > > .. so in theory the sparc64 stuff may just be: > > > > pkg install sparc64-gcc sparc64-xtoolchain-gcc > > make <existing stuff> NO_WERROR=1 CROSS_TOOLCHAIN=sparc64-gcc buildworld > > > When I added the cross toolchain it was first tested on sparc64 and people > reported that it built and run fine with it. > > This was with gcc 4.9, I haven't tested with 5.2 Should we perhaps looking at switching the default toolchain for sparc64 to external similar to how we require external binutils for aarch64? (Require some sort of explicit make variable on HEAD to permit building with GCC 4.2.1?) -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3293168.mJnTOSukKj>