From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Aly Dharshi <aly.dharshi@edmonton.ca>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Sphinx Errors on CentOS 7
Date: Wed, 05 Oct 2016 16:18:01 +0200 [thread overview]
Message-ID: <1489902.QG88RjLba8@xps13> (raw)
In-Reply-To: <CANQcpR4kCT-4MzQOHfGfHYs4jc2pmeVJyz1YcRzwwVD844V51g@mail.gmail.com>
2016-10-05 08:09, Aly Dharshi:
> Hello DPDK Users,
>
> I am building an rpm set using the bundled SPEC file. Everything
> compiles fine except the sphinx part:
[...]
> I've had to do this in the spec file to generate the build:
>
> BuildRequires: kernel-devel, kernel-headers, libpcap-devel, xen-devel
> BuildRequires: doxygen, python-sphinx, inkscape
> #BuildRequires: texlive-collection-latexextra
>
> This is because it seems that texlive-collection-latexextra does not
> exist on CentOS 7.2. Is there anyway to proceed:
>
> 1. How do I resolve the sphinx error ?
It is really hard to know what's going wrong with PDF generation.
You can try "make doc V=1"
> 2. Can I simply build this kit without docs ?
Yes you can remove the line "make O=%{target} doc" from the spec file.
next prev parent reply other threads:[~2016-10-05 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:09 Aly Dharshi
2016-10-05 14:18 ` Thomas Monjalon [this message]
2016-10-05 14:27 ` Aly Dharshi
2016-10-05 14:32 ` Aly Dharshi
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=1489902.QG88RjLba8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=aly.dharshi@edmonton.ca \
--cc=users@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).