On 20 April 2018 at 15:15, Pavel Machek <pavel@xxxxxx> wrote: > Hi! > >> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to >> >> a particular subset of arm architectures? (My local builds of arm all >> >> succeed, for example. Can you send your failing config?) I'll take a >> >> closer look on Monday if Daniel doesn't beat me to it. >> > >> > Daniel, Kees: any news? >> > >> > I'm aware you did not specify which Monday :-). >> >> Hi! Sorry, I got distracted. So the .config you sent me builds fine >> with my cross compiler. I suspect this is something specific to ELDK's >> compiler. I can try some other compiler versions. What version of gcc >> is failing? > > I have: > > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-gcc --version > arm-linux-gnueabi-gcc (GCC) 4.7.2 > Copyright (C) 2012 Free Software Foundation, Inc. > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-ld --version > GNU ld (GNU Binutils) 2.23.1.20121113 > Copyright 2012 Free Software Foundation, Inc. > > Let me try with eldk-5.6: > > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-gcc --version > arm-linux-gnueabi-gcc (GCC) 4.8.2 > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-ld --version > GNU ld (GNU Binutils) 2.24 > > make lib/string.o > > Seems to succeed, so I guess full build will succeed, too... It doesn't imply that a full build would work. -- 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
