All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: James Harvey <jamespharvey20@gmail.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: v25.0 ninja install failure on pandoc-prebuilt using git tree or release tarball
Date: Wed, 7 Aug 2019 09:22:46 -0300	[thread overview]
Message-ID: <20190807122246.GD1557@ziepe.ca> (raw)
In-Reply-To: <CA+X5Wn75Lfh_i89sW1L+x1S3rnZsEGkzfNYju4woPvq0yCo=XA@mail.gmail.com>

On Tue, Aug 06, 2019 at 11:45:21PM -0400, James Harvey wrote:

> As-is, building v25 from the git repo has a new build requirement of
> rst2man, which isn't documented in the release notes or in the readme.
> (On Arch, part of the python-docutils package.)  I haven't directly
> used pandoc or rst2man before, so I don't know if rst2man was added to
> be an alternative to pandoc, or ran in addition to it. 

Both are required.

> I looked at switching to the release tarballs (rdma-core-25.0.tar.gz),
> which of course has the prebuilt man pages.  I assume doing this
> should completely prevent needing pandoc and rst2man.  But, then
> "ninja install" fails from not finding
> "pandoc-prebuilt/32acf8c8016edc90e7adedc5be9caecd9b8abb3e", which I do
> see is not among the 81 directories in "pandoc-prebuilt/" in
> "rdma-core-25.0.tar.gz".  Were some of the necessary prebuilt files
> not included in the 25 tarball?

Hum, it will be hard to tell what is going wrong without knowing what
is in that file - if you have pandoc and rst2man installed then
build/pandoc-rebuilt should contain it.

Jason

      parent reply	other threads:[~2019-08-07 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  3:45 v25.0 ninja install failure on pandoc-prebuilt using git tree or release tarball James Harvey
2019-08-07  7:29 ` Leon Romanovsky
2019-08-07 12:22 ` Jason Gunthorpe [this message]

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=20190807122246.GD1557@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=jamespharvey20@gmail.com \
    --cc=linux-rdma@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.