From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masami Hiramatsu Subject: Re: linux-next: build warnings from the build of Linus' tree Date: Sat, 25 Aug 2018 10:51:27 +0900 Message-ID: <20180825105127.7d178290162a186a7c768c60@kernel.org> References: <20180824133206.4218c2e5@canb.auug.org.au> <20180824172053.20fa197294f51496dcec5605@kernel.org> <20180824204756.e787765461975cd1e27502dc@kernel.org> <20180824224211.2934d7c0@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180824224211.2934d7c0@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: "Steven Rostedt (VMware)" , Linux-Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org On Fri, 24 Aug 2018 22:42:11 +1000 Stephen Rothwell wrote: > Hi Masami, > > On Fri, 24 Aug 2018 20:47:56 +0900 Masami Hiramatsu wrote: > > > > gcc-7.3.0 cross build ld shows below warnings. > > > > MODPOST vmlinux.o > > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'. > > KSYM .tmp_kallsyms1.o > > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'. > > KSYM .tmp_kallsyms2.o > > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'. > > KSYM .tmp_kallsyms3.o > > LD vmlinux > > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'. > > I reported those a while ago when I started using the native Debian gcc > on my Powerpc build box. > > > But it seems another warning, and I couldn't see your warnings. Could you tell me your gcc version? > > Currently, it is the Debian gcc 8.2.0, ld 2.31.1. Hmm, so I guess it might be related to newer gcc (8?). I need to check it on x86-64 too. Thank you, -- Masami Hiramatsu