linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings from the build of Linus' tree
Date: Sun, 26 Aug 2018 17:10:58 +0900	[thread overview]
Message-ID: <20180826171058.e07f99e6e03f7497e5a46ed3@kernel.org> (raw)
In-Reply-To: <20180824224211.2934d7c0@canb.auug.org.au>

Hi Stephen,

On Fri, 24 Aug 2018 22:42:11 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Masami,
> 
> On Fri, 24 Aug 2018 20:47:56 +0900 Masami Hiramatsu <mhiramat@kernel.org> 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, unfortunately, I couldn't reproduce the ".data..LPBX1" error with
my gcc-8.1.0 + ld-2.30 distributed at https://cdn.kernel.org/pub/tools/crosstool/.
Could you also try to enable CONFIG_GCOV_PROFILE_ALL=y and build the kernel?
If it causes similar error, it should be caused by gcov support.

Thank you,

-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2018-08-26  8:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  3:32 linux-next: build warnings from the build of Linus' tree Stephen Rothwell
2018-08-24  8:20 ` Masami Hiramatsu
2018-08-24 11:47   ` Masami Hiramatsu
2018-08-24 12:42     ` Stephen Rothwell
2018-08-25  1:51       ` Masami Hiramatsu
2018-08-26  8:10       ` Masami Hiramatsu [this message]
2018-08-27 21:23         ` Stephen Rothwell
2018-08-28  0:43           ` Masami Hiramatsu
2018-09-06 10:49             ` Peter Oberparleiter
2018-09-06 16:42               ` Masami Hiramatsu
2018-09-07 12:50                 ` Peter Oberparleiter
2018-09-08  3:57                   ` Masami Hiramatsu
2018-09-10 13:27                     ` Peter Oberparleiter
2018-09-11 11:49                       ` Masami Hiramatsu
2018-09-11 14:10                         ` Masami Hiramatsu
2018-09-06 22:14               ` Stephen Rothwell
2018-09-07  3:34                 ` Stephen Rothwell
2018-10-11  0:48               ` Stephen Rothwell
2018-10-11  7:44                 ` Peter Oberparleiter
2018-10-11  9:58                   ` Stephen Rothwell
2018-10-11 10:37                     ` Greg KH
2018-10-11 11:09                       ` Peter Oberparleiter
2018-10-11 13:54                       ` Arnd Bergmann
2018-10-11 22:12                         ` [GIT PULL] A couple of warning fixes Stephen Rothwell
2018-10-12 10:51                           ` Greg KH
2018-08-24 12:46   ` linux-next: build warnings from the build of Linus' tree Arnd Bergmann
2018-08-25 18:53     ` Masami Hiramatsu
2018-08-25 19:53       ` Arnd Bergmann
2018-09-01  9:50         ` Masami Hiramatsu
2018-09-01 12:38           ` [PATCH] ARM: linker script: GCOV kernel may refers data in __exit Masami Hiramatsu
2018-09-11 14:12             ` Masami Hiramatsu
2018-08-29  2:11     ` linux-next: build warnings from the build of Linus' tree Greentime Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180826171058.e07f99e6e03f7497e5a46ed3@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).