public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: debugging kbuild
Date: Tue, 7 Aug 2018 05:08:22 -0500	[thread overview]
Message-ID: <20180807100822.GD31204@gate.crashing.org> (raw)
In-Reply-To: <CAKwvOdkozP4t3AusfnKfrTmhyrXh4JW4m-ersfnoeTWXcMfJSw@mail.gmail.com>

On Mon, Aug 06, 2018 at 04:31:14PM -0700, Nick Desaulniers wrote:
> Is there a way to print the exact command that's being invoked from
> Make? For example, some of the macro's in scripts/Kbuild.include are
> tricky to unwind. Is there a way to dump each sub command being run?

There always is strace...  Or maybe  make -dj  and friends.


Segher

  parent reply	other threads:[~2018-08-07 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 23:31 debugging kbuild Nick Desaulniers
2018-08-06 23:40 ` Randy Dunlap
2018-08-07 10:08 ` Segher Boessenkool [this message]
2018-08-07 16:29   ` Nick Desaulniers
2018-08-07 16:31     ` Randy Dunlap

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=20180807100822.GD31204@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox