Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH] Fix regression in improvement of build scripts
Date: Mon, 25 Apr 2016 21:20:04 +0900	[thread overview]
Message-ID: <571E0B74.6030808@gmail.com> (raw)

Hi, Paul.

I realized there was a real regression in the runlatex refactoring
patch.

Attached is the obvious fix.
I hope nobody has been affected by the bug.
Please apply.
                                                   Thanks, Akira

---
From 816c5fb3ae9bf1ad18e622cbee327aca1df66629 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiysw@gmail.com>
Date: Mon, 25 Apr 2016 20:47:31 +0900
Subject: [PATCH] Fix regression in improvement of build scripts

In commit 4038e781ed56 ("Improve behavior of build scripts"),
I made an obvious error in the dependency of 'perfbook.aux.'
This commit fixes it.

Signed-off-by: Akira Yokosawa <akiysw@gmail.com>
---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 7202334..b909c81 100644
--- a/Makefile
+++ b/Makefile
@@ -173,7 +173,7 @@ perfbook.pdf: perfbook.bbl $(LATEXSOURCES) $(EPSSOURCES) extraction embedfonts
 perfbook.bbl: $(BIBSOURCES) perfbook.aux
 	bibtex perfbook

-perfbook.aux: $(LATEXSOURCES) $(EPSSOURCES)
+perfbook.aux: $(LATEXSOURCES) $(EPSSOURCES) extraction embedfonts
 	sh utilities/runfirstlatex.sh perfbook

 perfbook-1c.pdf: perfbook-1c.bbl $(LATEXSOURCES) $(EPSSOURCES) extraction embedfonts
-- 
1.9.1


             reply	other threads:[~2016-04-25 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 12:20 Akira Yokosawa [this message]
2016-04-25 17:21 ` [PATCH] Fix regression in improvement of build scripts Paul E. McKenney

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=571E0B74.6030808@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=perfbook@vger.kernel.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