From: Masaru Oki <m-oki@stratosphere.co.jp>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Cannot build doc using DPDK-2.0.0-rc3
Date: Wed, 1 Apr 2015 19:13:36 +0900 [thread overview]
Message-ID: <CAFLKUzJsf4n-K=2Z2MAkZAS05YN++Afd+GUYKyHJ-5U805=5rw@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F00BB1@IRSMSX103.ger.corp.intel.com>
Hi,
guide-% rule is selected instead of guide-pdf-% in mk/rte.sdkdoc.mk, I guess.
2015-04-01 19:08 GMT+09:00 Mcnamara, John <john.mcnamara@intel.com>:
>> -----Original Message-----
>> From: Tetsuya Mukawa [mailto:mukawa@igel.co.jp]
>> Sent: Wednesday, April 1, 2015 10:49 AM
>> To: De Lara Guarch, Pablo; Mcnamara, John
>> Cc: dev@dpdk.org
>> Subject: Re: [dpdk-dev] Cannot build doc using DPDK-2.0.0-rc3
>>
>> I am using Ubuntu14, so package name may be different.
>>
>> To make sure, I just installed 'texlive-*', then tried to build doc again.
>> But I faced the same error.
>> Anyway, it seems the error comes from my environment, so I will check it
>> more.
>
> Hi,
>
> Actually that looks like a Makefile issue rather than a toolchain issue. Sphinx shouldn't be trying to build with a builder called "pdf-freebsd_gsg". It seems that it has picked up the wrong rule.
>
> I'll look into it.
>
> John
next prev parent reply other threads:[~2015-04-01 10:13 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 [this message]
2015-04-01 10:49 ` Mcnamara, John
2015-04-01 11:13 ` Mcnamara, John
2015-04-02 1:04 ` Tetsuya Mukawa
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='CAFLKUzJsf4n-K=2Z2MAkZAS05YN++Afd+GUYKyHJ-5U805=5rw@mail.gmail.com' \
--to=m-oki@stratosphere.co.jp \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).