From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 182] make doc-guides-pdf fails with error 'make[3]: latexmk: Command not found'
Date: Mon, 07 Jan 2019 06:26:20 +0000 [thread overview]
Message-ID: <bug-182-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=182
Bug ID: 182
Summary: make doc-guides-pdf fails with error 'make[3]:
latexmk: Command not found'
Product: DPDK
Version: 19.02
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
Issue:
1. Install all packages for Ubuntu
'http://doc.dpdk.org/guides/contributing/documentation.html' for documentation
2. for target 'make doc-guides-pdf'
Error:
pdflatex processing guides-pdf-faq...
make[3]: latexmk: Command not found
Makefile:33: recipe for target 'doc.pdf' failed
make[3]: *** [doc.pdf] Error 127
Work around: apt install latexmk (for ubuntu)
Request: update section to install 'latexmk' for ubuntu
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-01-07 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 6:26 bugzilla [this message]
2019-05-06 4:32 ` bugzilla
2019-05-06 4:32 ` bugzilla
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=bug-182-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).