On Wed, Jul 16, 2014 at 9:47 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Nick, > > On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause <xerofoify@xxxxxxxxx> wrote: >> >> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause <xerofoify@xxxxxxxxx> wrote: >> >> >> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> >> > >> >> > Status of my local build tests will be at >> >> > http://kisskb.ellerman.id.au/linux-next . >> > >> >> I am trying to get the maintainers to clean up still failing builds. >> >> When you get time I wondering >> >> if you can send me a list of still failing builds and warnings of >> >> interest in the kernel that is' >> >> up to date for me to help clean up these outstanding issues with the >> >> maintainers support as needed. >> > >> > See above ... >> >> There seems to be a few that are still succeeding for me that aren't for. >> Would you mind testing some of them again to see if they are succeeding >> with a gcc compiler that is newer then version 4.7. > > Please tell us exactly what you are testing: what kernel version, what > compiler/binutils version. The kernel is meant to be able to be built > with gcc 4.7 (and some earlier) - barring compiler bugs, of course. > > -- > Cheers, > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx Absolutely , I am using the latest kernel rc from git. I am using gcc 4.8.3 and binutils 2.83.91. In addition I am using the default configurations as you are in less I am doing it differently. By the way xtensa-defconfig seems to fail because of binutils as I discussed this with the maintainers and they seemed to have tested it with a newer upstream binutils then I am using and it succeeded it the linking failures I am seeing with it. Cheers Nick -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
