From: Aly Dharshi <aly.dharshi@edmonton.ca>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Sphinx Errors on CentOS 7
Date: Wed, 5 Oct 2016 08:27:47 -0600 [thread overview]
Message-ID: <CANQcpR4ZeGwtsJ-qERx5TocZuUHNdbkVBeNx02fEczF9_t-Qmg@mail.gmail.com> (raw)
In-Reply-To: <1489902.QG88RjLba8@xps13>
Thanks Thomas,
I am trying option 2 with the like commented out. I am running into :
Processing files: dpdk-devel-16.07-1.x86_64
Provides: dpdk-devel = 16.07-1 dpdk-devel(x86-64) = 16.07-1
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: /bin/bash /bin/echo /bin/sh /usr/bin/python2
libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) rtld(GNU_HASH)
Processing files: dpdk-doc-16.07-1.noarch
error: File not found:
/root/rpmbuild/BUILDROOT/dpdk-16.07-1.x86_64/usr/share/doc/dpdk
RPM build errors:
File not found:
/root/rpmbuild/BUILDROOT/dpdk-16.07-1.x86_64/usr/share/doc/dpdk
Any thoughts ? Should I be building the RPM in a specific dir like
/usr/src ? Thanks.
Cheers,
ASD.
---
Aly Dharshi B.Sc. RHCE.
LRT Communications Design Specialist
Engineering & Maintenance
City Operations | Edmonton Transit System
780.496.2869 telephone
780.619.1595 mobile
City Of Edmonton
DL MacDonald Transit Yards
ROW Building
13304 50A Street
Edmonton AB T5A 4P6
All information contained in this email post is proprietary to the
City of Edmonton, confidential and intended only for the addressed
recipient. If you have received this post in error, please disregard
the contents, inform the sender of the misdirection, and remove it
from your system. The copying, dissemination or distribution of this
email, if misdirected, is strictly prohibited.
On Wed, Oct 5, 2016 at 8:18 AM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 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:28 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
2016-10-05 14:27 ` Aly Dharshi [this message]
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=CANQcpR4ZeGwtsJ-qERx5TocZuUHNdbkVBeNx02fEczF9_t-Qmg@mail.gmail.com \
--to=aly.dharshi@edmonton.ca \
--cc=thomas.monjalon@6wind.com \
--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).