DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/5] mk: reduce PDF build commands
Date: Thu,  2 Apr 2015 21:58:19 +0200	[thread overview]
Message-ID: <1428004702-8987-3-git-send-email-thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1428004702-8987-1-git-send-email-thomas.monjalon@6wind.com>

In case of documents without image, an empty rm command can be seen if V=1.
Remove it to avoid disturbing debugging.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 mk/rte.sdkdoc.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mk/rte.sdkdoc.mk b/mk/rte.sdkdoc.mk
index f91e079..9952f25 100644
--- a/mk/rte.sdkdoc.mk
+++ b/mk/rte.sdkdoc.mk
@@ -99,7 +99,7 @@ guides-pdf-%:
 	$(Q)$(RTE_SPHINX_BUILD) -b latex $(RTE_SPHINX_VERBOSE) \
 		-c $(RTE_SDK)/doc/guides $(RTE_SDK)/doc/guides/$* \
 		$(RTE_OUTPUT)/doc/pdf/guides/$*
-	$(Q)rm -f $^
+	$(if $^,$(Q)rm -f $^)
 	@echo 'pdflatex processing $@...'
 	$(Q)$(MAKE) all-pdf -sC $(RTE_OUTPUT)/doc/pdf/guides/$* \
 		LATEXOPTS=$(RTE_PDFLATEX_VERBOSE)
-- 
2.2.2

  parent reply	other threads:[~2015-04-02 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 19:58 [dpdk-dev] [PATCH 0/5] packaging release 2.0.0 Thomas Monjalon
2015-04-02 19:58 ` [dpdk-dev] [PATCH 1/5] mk: remove fuse requirement for vhost-user Thomas Monjalon
2015-04-02 19:58 ` Thomas Monjalon [this message]
2015-04-03  8:20   ` [dpdk-dev] [PATCH 2/5] mk: reduce PDF build commands Butler, Siobhan A
2015-04-02 19:58 ` [dpdk-dev] [PATCH 3/5] pkg: remove -core file suffix Thomas Monjalon
2015-04-02 19:58 ` [dpdk-dev] [PATCH 4/5] pkg: update RPM Thomas Monjalon
2015-04-02 19:58 ` [dpdk-dev] [PATCH 5/5] version: 2.0.0 Thomas Monjalon
2015-04-03 14:15 ` [dpdk-dev] [PATCH 0/5] packaging release 2.0.0 Thomas Monjalon

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=1428004702-8987-3-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    /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).