From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:45969 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750808AbcAOW7G (ORCPT ); Fri, 15 Jan 2016 17:59:06 -0500 Date: Fri, 15 Jan 2016 22:59:01 +0000 From: Al Viro To: kbuild test robot Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org Subject: Re: [vfs:asm-exports 1/8] arch/avr32/lib/built-in.o: warning: input is not relaxable Message-ID: <20160115225901.GH17997@ZenIV.linux.org.uk> References: <201601160451.RTseDQbE%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201601160451.RTseDQbE%fengguang.wu@intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Jan 16, 2016 at 04:48:53AM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git asm-exports > head: 7edee3610000e590052ed9c4e1c97ed0c491e776 > commit: 22319e98abd25dc2039b255def816bdef461c40a [1/8] [kbuild] handle exports in lib-y objects reliably > config: avr32-atngw100_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 > git checkout 22319e98abd25dc2039b255def816bdef461c40a > # save the attached .config to linux build tree > make.cross ARCH=avr32 > > All warnings (new ones prefixed by >>): > > >> arch/avr32/lib/built-in.o: warning: input is not relaxable > virt/built-in.o: warning: input is not relaxable > >> arch/avr32/lib/built-in.o: warning: input is not relaxable > virt/built-in.o: warning: input is not relaxable > >> arch/avr32/lib/built-in.o: warning: input is not relaxable > virt/built-in.o: warning: input is not relaxable Interesting... Looks like avr ld decides to complain about the (empty, contains only externs) lib-exports.o. No sections in there, but since the damn thing is not marked relaxable in ELF headers, ld assumes that there has to be an unsuitable section somewhere... No, wait - those new warnings are not new at all; they are just added to the pile of similar ones from other built-in.o. Could you give me an URL of full build log?