All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: make clean all broken with -j? + question regarding modpost
Date: Sat, 12 Aug 2017 13:21:26 +0200	[thread overview]
Message-ID: <20170812112126.GB7704@localhost.localdomain> (raw)
In-Reply-To: <CAK7LNARwaZJv62LEqBv5BiGsV9r4TdeNZ41bWH2H-cXA6g7WzA@mail.gmail.com>

On Sat, Aug 12, 2017 at 12:15:11PM +0900, Masahiro Yamada wrote:
> Hi.
> 
> 2017-08-11 3:28 GMT+09:00 Randy Dunlap <rdunlap@infradead.org>:
> 
> >> 2.) compile modpost with debug symbols, -g
> >> how do I compile the modpost helper program with debug symbols? In what
> >> makefile, kbuild file do I need to add the compiler flag?
> >> Any help would be appreciated!
> 
> 
> If you want to pass extra options to the build command of host-programs,
> HOST_EXTRACFLAGS is supported.
> 
> For example,  HOST_EXTRACFLAGS=-g

Yes, after reading Documentation/kbuild/makefiles.txt and studying the
top level Makefile I was able to figure it out by myself.

But many thanks for the hint!

Now I just need to find out why an UML kernel with CONFIG_GCOV fails to
build all modules. modpost abends with missing symbols
__gcov_init, etc.


with kind regards
thomas
> 
> 
> 
> 
> 
> -- 
> Best Regards
> Masahiro Yamada

  reply	other threads:[~2017-08-12 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 15:42 make clean all broken with -j? + question regarding modpost Thomas Meyer
2017-08-10 18:28 ` Randy Dunlap
2017-08-10 22:11   ` Jim Davis
2017-08-12  3:11     ` Masahiro Yamada
2017-08-12  8:06       ` Sam Ravnborg
2017-08-12 11:13       ` Thomas Meyer
2017-08-12  3:15   ` Masahiro Yamada
2017-08-12 11:21     ` Thomas Meyer [this message]
2017-08-10 22:58 ` valdis.kletnieks

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=20170812112126.GB7704@localhost.localdomain \
    --to=thomas@m3y3r.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=yamada.masahiro@socionext.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.