DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	 Masaru Oki <m-oki@stratosphere.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Cannot build doc using DPDK-2.0.0-rc3
Date: Thu, 02 Apr 2015 10:04:19 +0900	[thread overview]
Message-ID: <551C9593.70105@igel.co.jp> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F00C2E@IRSMSX103.ger.corp.intel.com>

On 2015/04/01 20:13, Mcnamara, John wrote:
>> -----Original Message-----
>> From: Masaru Oki [mailto:m-oki@stratosphere.co.jp]
>> Sent: Wednesday, April 1, 2015 11:14 AM
>> To: Mcnamara, John
>> Cc: Tetsuya Mukawa; De Lara Guarch, Pablo; dev@dpdk.org
>> Subject: Re: [dpdk-dev] Cannot build doc using DPDK-2.0.0-rc3
>>
>>
>> guide-% rule is selected instead of guide-pdf-% in mk/rte.sdkdoc.mk, I
>> guess.
> Hi,
>
> Changing the order of the guide-pdf-% and guide-% rules fixes the issue with make 3.81. I'll submit a patch.
>
> John

Hi John and Oki-san,

Thanks, I made sure I could build doc.

Tetsuya

  reply	other threads:[~2015-04-02  1:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01  9:17 Tetsuya Mukawa
2015-04-01  9:29 ` De Lara Guarch, Pablo
2015-04-01  9:49   ` Tetsuya Mukawa
2015-04-01 10:08     ` Mcnamara, John
2015-04-01 10:13       ` Masaru Oki
2015-04-01 10:49         ` Mcnamara, John
2015-04-01 11:13         ` Mcnamara, John
2015-04-02  1:04           ` Tetsuya Mukawa [this message]
2015-04-01 11:32 ` [dpdk-dev] [PATCH] mk: fix for "make doc-guides-pdf" with make 3.81 John McNamara
2015-04-01 12:07   ` De Lara Guarch, Pablo
2015-04-01 12:31   ` [dpdk-dev] [PATCH v2] mk: fix pdf doc rules order Thomas Monjalon
2015-04-01 13:29     ` Mcnamara, John
2015-04-01 19:22       ` 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=551C9593.70105@igel.co.jp \
    --to=mukawa@igel.co.jp \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=m-oki@stratosphere.co.jp \
    /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).