All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] graph-depends: support calling from recursive make
Date: Sun, 29 Jun 2014 10:44:23 +0200	[thread overview]
Message-ID: <20140629104423.0875c8f7@free-electrons.com> (raw)
In-Reply-To: <1403554284-4935-1-git-send-email-arnout@mind.be>

Dear Arnout Vandecappelle (Essensium/Mind),

On Mon, 23 Jun 2014 22:11:23 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The graph-depends script calls make. If the outer make was called
> recursively, or if it was called with '-C <somedir>', then the
> environment will contain "MAKEFLAGS=w --". Therefore, the recursive
> make prints 'Entering' and 'Leaving' messages, which clobbers the
> output for dot.
> 
> To avoid this, add "--no-print-directory" to the recursive make
> arguments. Since we require GNU make 3.81, we can be sure that this
> option is available.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

Patches 1/2 and 2/2 applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-06-29  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 20:11 [Buildroot] [PATCH 1/2] graph-depends: support calling from recursive make Arnout Vandecappelle
2014-06-23 20:11 ` [Buildroot] [PATCH 2/2] graph-depends: remove unnecessary redirect of stderr Arnout Vandecappelle
2014-06-23 20:42   ` Yann E. MORIN
2014-06-23 21:13     ` Samuel Martin
2014-06-23 20:29 ` [Buildroot] [PATCH 1/2] graph-depends: support calling from recursive make Yann E. MORIN
2014-06-29  8:44 ` Thomas Petazzoni [this message]

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=20140629104423.0875c8f7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.