Date: Mon, 10 Aug 2015 11:00:54 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Jordan Hubbard <jordanhubbard@me.com> Cc: Adrian Chadd <adrian.chadd@gmail.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "K. Macy" <kmacy@freebsd.org>, Kevin Bowling <kevin.bowling@kev009.com>, Bill Sorenson <instructionset@gmail.com> Subject: Re: Sparc64 support Message-ID: <20150810090054.GF96980@ivaldir.etoilebsd.net> In-Reply-To: <926DDA42-8883-4AB4-B229-D44387FF5C6B@me.com> References: <mq3sg1$bno$1@ger.gmane.org> <CACcTwYnU=E-6sV3yLh3yKUSPZOg7967XV5ToXoSVPuNfOjF7hQ@mail.gmail.com> <CAHM0Q_NEYWxpHCwEdytfY6i9%2BRO2BebezzmenfQ_1c4u7zGrgg@mail.gmail.com> <CACcTwY=DcUREt5nJWo_eJfrB=3sQXBaS6nc%2B07fpZhxARD0zTQ@mail.gmail.com> <20150809215403.GC20238@server.rulingia.com> <6C12EBFE-EAA9-4C12-9F03-1CB2C28C4A6E@me.com> <CACcTwYktQRTqVSr7PRr5huwbVXVu6oCy26TKiAxzf2NiGAcocA@mail.gmail.com> <51EEBC6E-5D85-439D-874D-D223EE045515@me.com> <CAJ-VmomzV0YKQwenwSZv6fMAOUP8TmPs-oyQaM8KTF7Ndhv_%2Bw@mail.gmail.com> <926DDA42-8883-4AB4-B229-D44387FF5C6B@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--w3uUfsyyY1Pqa/ej Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 09, 2015 at 09:34:33PM -0700, Jordan Hubbard wrote: >=20 > > On Aug 9, 2015, at 8:48 PM, Adrian Chadd <adrian.chadd@gmail.com> wrote: > >=20 > > What's missing is someone funding / finishing the push to external > > toolchain support for all platforms. >=20 > Does someone have that condensed down to a set of bullet points? Which p= latforms are mandatory and which are optional? Is the task considered done= when one can do: Well external toolchain is know to work properly with sparc64 (without patc= hes) with mips with patches, I used to work with powerpc64 (haven't tried others= ). This was based on gcc 4.9 and has been updated to 5.2 recently. What is missing so far is the chicken egg problem that happen once you have= boot your newly built FreeBSD because you do not have a compiler, one would need= to work on a mechanism to be able to provide at least all the set of packages = until having a working compiler so one can pkg install gcc. (there is work in that direction but not that much, at least now installworld is installing stuff = this is usable as a sysroot (in 99% of the cases)). >=20 > # cd /usr/src > # make buildworld buildkernel USE_EXT_TOOLCHAIN=3Dyes EXT_TOOLCHAIN_PORT= =3Dgcc-4.9 (or whatever the suitable incantation is?) >=20 > Does it have to work for multiple values of =E2=80=9Cexternal toolchain= =E2=80=9D? Is it a safe assumption to just say that =E2=80=9Cport install = FOO=E2=80=9D will be a sufficient prerequisite and /usr/local/bin/cc is all= one needs to reference as the right compiler driver (for the C stuff obvio= usly). >=20 > If anyone is going to fund anything, they will want a very specific set o= f deliverables to fund, since it=E2=80=99s otherwise kind of a blank check = with a completely arbitrary outcome. >=20 > > What's also missing a little bit here is the tier-1-ness of the > > external toolchain support by the people using/developing other > > toolchains. >=20 > Not sure what that means? me neither :) >=20 > > It's basically there. There are some rough edges, but since the > > compiler-developer people aren't using it and the non-x86-building > > people aren't being forced to use it, the development inches along > > very slowly. >=20 > Again, maybe you could qualify just what that means. I don=E2=80=99t kno= w what moving parts are even really being described here. My life is clang= / LLVM and has been for a very long time - I don=E2=80=99t even know what = gcc is anymore. :) >=20 > > If you'd like to erm, "rush" this along, we should actively start the > > "deorbit gcc-4.2 by freebsd-11" and "disconnect gcc-4.2 from the -head > > build" movement now, get those bits done, and start arm-twisting to > > get the last bits finished. >=20 > If gcc 4.2 de-orbits then that means that clang / LLVM can take its place= as the =E2=80=9Cdefault toolchain=E2=80=9D in base and any other value of = GCC (which?) comes from ports? > That is the plan Best regards, Bapt --w3uUfsyyY1Pqa/ej Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlXIaEYACgkQ8kTtMUmk6EyuXACeOVt268VducpnlIBmcbxC9EoB kvAAni5lX+HlnM2FeEGUqCPqGVD5JY9y =dJkE -----END PGP SIGNATURE----- --w3uUfsyyY1Pqa/ej--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150810090054.GF96980>