public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "Thorben Römer" <thorben.roemer@secunet.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: install-step fails for pandoc-prebuilt man-pages in infiniband-diags/man
Date: Thu, 5 Dec 2019 10:12:27 +0200	[thread overview]
Message-ID: <20191205081227.GB4939@unreal> (raw)
In-Reply-To: <5d754108-7020-6041-1b7d-bbb3fb2f089b@secunet.com>

On Wed, Dec 04, 2019 at 03:34:14PM +0100, Thorben Römer wrote:
> I tested the following on release 0.26.0 and 0.26.1, with the *.tar.gz
> provided on github. It is probably relevant for a lot more released
> archives and future releases. My build environment is restricted and
> does not have access to pandoc or rst2man.
>
> The command 'ninja install' fails in environments without pandoc and/or
> rst2man. There is an automatic fallback to use man-pages in
> buildlib/pandoc-prebuilt that are added for every release-archive.
> However, the install step fails with error such as:
>
> CMake Error at infiniband-diags/man/cmake_install.cmake:40 (file):
> file INSTALL cannot find
> "rdma-core-26.0/buildlib/pandoc-prebuilt/64a3de4dd91635b29f4f8d11a987670751827c60".
> Call Stack (most recent call first):
> cmake_install.cmake:166 (include)

We don't support any make/ninja install flows and you posted one of the possible failures.

There are three recommended ways to build and install rdma-core:
1. For run in-place (without install) - use build.sh - recommended way.
2. For properly created RPM/DEB packages for other OSes - use buildlib/cbuild script.
3. For RPMs created for this OS - use "rpmbuild --build-in-place -bb redhat/rdma-core.spec"

Fro step 2 and 3, installation is done with those RPMs/DEBs.

Thanks

  reply	other threads:[~2019-12-05  8:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 14:34 install-step fails for pandoc-prebuilt man-pages in infiniband-diags/man Thorben Römer
2019-12-05  8:12 ` Leon Romanovsky [this message]
2019-12-09 19:39 ` Jason Gunthorpe
2019-12-10  7:31   ` Thorben Römer
2019-12-10 17:29     ` Jason Gunthorpe

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=20191205081227.GB4939@unreal \
    --to=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=thorben.roemer@secunet.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