Messages in this thread | | | From | Kees Cook <> | Date | Fri, 23 Jun 2017 11:35:56 -0700 | Subject | Re: enabling COMPILE_TEST support for GCC plugins in v4.11 |
| |
On Thu, Jun 22, 2017 at 10:43 PM, Michael Ellerman <mpe@ellerman.id.au> wrote: > [Old thread just popped up in my inbox] > > Kees Cook <keescook@google.com> writes: >> On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker >> <paul.gortmaker@windriver.com> wrote: >>> On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook <keescook@google.com> wrote: >>>> Hi, >>>> >>>> I'd like to get the GCC plugins building under >>>> allyesconfig/allmodconfig for -next soon (with the intention of >>>> landing the change in v4.11). Specifically, I intend to revert >>>> a519167e753e ("gcc-plugins: disable under COMPILE_TEST"). >>> >>> If I recall correctly, I noted that the plugins broke the kernel.org >>> cross compiler toolchains which led to the above disable. >> >> Do you mean these? >> https://www.kernel.org/pub/tools/crosstool/ > > I think those are the ones Paul is talking about. > > Those were mostly built by Tony, who is know, sadly, an Openstack > developer and for some reason doesn't seem to have time to build > toolchains for kernel hackers :P > > > As folks may have seen on LWN, there are now pre-built toolchains for > many architectures available from the Free Electrons guys, so that may > help to unblock this situation somewhat: > > http://toolchains.free-electrons.com/
Perhaps we should add a link in pub/tools/crosstool/ ? 4.6.3 is pretty old at this point, but the Free Electrons toolchains don't include some of the less used architectures.
-Kees
-- Kees Cook Pixel Security
| |