From: Robert Richter <rric@kernel.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix output directory of Documentation/
Date: Thu, 27 Jun 2013 13:47:08 +0200 [thread overview]
Message-ID: <20130627114708.GF21788@rric.localhost> (raw)
In-Reply-To: <20130621124939.GB11635@rric.localhost>
On 21.06.13 14:50:20, Robert Richter wrote:
> On 20.06.13 12:26:03, Arnaldo Carvalho de Melo wrote:
> > Robert, so this one is with:
> >
> > cd tools/perf
> > make install-doc
> >
> > I tested with:
> >
> > make -C tools/perf O=/tmp/build/perf install-doc
> >
> > and it works, so it is just the in tree build that fails.
>
> The patch below fixes this. Thanks for reporting.
Arnaldo, I noticed this fix is not yet merge with:
79e10cb perf tools: Fix output directory of Documentation/
-Robert
> diff --git a/tools/perf/Documentation/Makefile b/tools/perf/Documentation/Makefile
> index 1368e88..5a37a7c 100644
> --- a/tools/perf/Documentation/Makefile
> +++ b/tools/perf/Documentation/Makefile
> @@ -271,7 +271,7 @@ $(MAN_HTML): $(OUTPUT)%.html : %.txt
>
> $(OUTPUT)%.1 $(OUTPUT)%.5 $(OUTPUT)%.7 : $(OUTPUT)%.xml
> $(QUIET_XMLTO)$(RM) $@ && \
> - $(XMLTO) -o $(OUTPUT) -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
> + $(XMLTO) -o $(OUTPUT). -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
>
> $(OUTPUT)%.xml : %.txt
> $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \
next prev parent reply other threads:[~2013-06-27 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 18:40 [PATCH] perf tools: Fix output directory of Documentation/ Robert Richter
2013-06-20 13:41 ` Jiri Olsa
2013-06-20 14:52 ` Arnaldo Carvalho de Melo
2013-06-20 14:58 ` Jiri Olsa
2013-06-20 15:26 ` Arnaldo Carvalho de Melo
2013-06-21 12:50 ` Robert Richter
2013-06-21 13:34 ` Arnaldo Carvalho de Melo
2013-06-21 14:02 ` Robert Richter
2013-06-27 11:47 ` Robert Richter [this message]
2013-07-12 8:49 ` [tip:perf/urgent] " tip-bot for Robert Richter
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=20130627114708.GF21788@rric.localhost \
--to=rric@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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