On 10/02/2015 12:04, David Ahern wrote: > Hello: > > I could use some help understanding a message from a kbuild robot. I submitted > this patch: > https://patchwork.ozlabs.org/patch/525102/ > > Which moves existing code into a function that is exported for modules. The > kbuild robot found this warning: > > ----- > > config: mips-nlm_xlp_defconfig (attached as .config) > reproduce: > wget > https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross > -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=mips > > All warnings (new ones prefixed by >>): > >>> mips-linux-gnu-ld: net/ipv4/.tmp_fib_semantics.o: warning: Inconsistent ISA >>> between e_flags and .MIPS.abiflags > > ----- > > I have no idea what that message means. I tried googling and found this recent > thread: > http://www.linux-mips.org/archives/linux-mips/2015-05/msg00156.html > and accompanying one: > https://sourceware.org/bugzilla/show_bug.cgi?id=18401 > > Can someone shed light on what the message means, why my patch generated the > message and better yet how to fix it? > > Thanks, > David Dunno if your patch generated the message per-say, but it seems some platforms in the MIPS tree cause this message to appear. I.e., IP27 or IP32 builds (or IP30 out-of-tree) don't emit this error, but building IP28 systems in-tree will cause it to appear quite a bit. The message itself, I believe is complaining that the stated CPU ISA (mips1 ... mips4, mips32r2, r10000, etc) in one of the sections (e.g.,.MIPS.abiflags) doesn't match the equivalent ISA value in the other section (e.g., e_flags). I haven't seen any harmful side effects of it myself. Seems to be more of a warning than anything else, and as long as the ISA matches a supported CPU (e.g., r10000 is compatible with mips4), it can be ignored. It does clutter up the build, though. --J
