Date: Fri, 7 Aug 2015 16:54:46 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Bill Sorenson <instructionset@gmail.com> Subject: Re: Sparc64 support Message-ID: <CAJ-VmomyKJaVhBR5=Dny%2BUpKoV6wmJJGNR6UKgjWq0UBRz=sMQ@mail.gmail.com> In-Reply-To: <7311511.ISQt3RZVgq@ralph.baldwin.cx> References: <CACcTwYmS1c5uoO-WiJQDwgqYAevX7WZ7ZrP297hnOu7cNET3CA@mail.gmail.com> <7311511.ISQt3RZVgq@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomyKJaVhBR5=Dny%2BUpKoV6wmJJGNR6UKgjWq0UBRz=sMQ>