[Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible pointer check into error] On 05/02/2016 (Fri 09:16) Daniel Wagner wrote: > On 02/01/2016 07:49 AM, Daniel Wagner wrote: > > On 01/29/2016 07:55 PM, Paul Gortmaker wrote: > >> [Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible pointer check into error] On 29/01/2016 (Fri 13:17) Daniel Wagner wrote: > >> > >>> On 01/28/2016 03:44 PM, Daniel Wagner wrote: > >>>> +# enforce correct pointer usage > >>>> +KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types) > >>>> + > >>> > >>> As it turns out there are a few fallouts by that one. I'll send fixes > >>> for it. > >> > >> Did you try non-x86 builds with this applied? I'd be really surprised > >> if there were just a few, once you did allyesconfig/allmodconfig for > >> ARM, MIPS, PPC, etc. > > > > I have tried this with non-x86 builds and apart of a few problems all > > looked fine. As it turns out I was using too old cross tools from > > kernel.org [1]. Luckily Fengguang's kbuild robot did catch a bunch of > > them (see the patches in this series). > > It turns out this week was particular bad for doing anything productive. > Anyway, I found some time to fire up some cross compilers and it looks > promising. > > I used the cross compiler version 5.2.1 shipped by Fedora 23 > and run allyesconfig/allmodconfig for ARM, ARM64, MIPS64, PPC64 > (swait-v7 and 4.5-rc2). No new errors popped up. SOunds good ; guess my gut feeling about this causing more fallout was off the mark. P. -- > > With some luck I get some more architectures covered soon. > > cheers, > daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
