From: Leon Romanovsky <leon@kernel.org>
To: "Bob Dröge" <b.e.droge@rug.nl>,
"Nicolas Morey-Chaisemartin" <NMoreyChaisemartin@suse.de>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Installation with prebuilt docs failing
Date: Thu, 18 Nov 2021 21:14:22 +0200 [thread overview]
Message-ID: <YZamDj1EqThLccyj@unreal> (raw)
In-Reply-To: <760b0992-776f-d35d-bbf3-6d7f351d0839@rug.nl>
On Thu, Nov 18, 2021 at 06:09:55PM +0100, Bob Dröge wrote:
> Hi,
>
> I'm trying to install rdma-core 37.1 from source on a Gentoo Prefix system
> which does not have pandoc nor rst2man installed. I'm using the release
> tarball from the GitHub release page (https://github.com/linux-rdma/rdma-core/releases/download/v37.1/rdma-core-37.1.tar.gz),
> though, and was expecting that it would use the prebuilt man pages in this
> case. However, this fails at some point with the following error:
>
> -- Installing: /cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/var/tmp/portage/sys-cluster/rdma-core-37.1/image/cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/usr/share/perl5/IBswcountlimits.pm
> -- Installing: /cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/var/tmp/portage/sys-cluster/rdma-core-37.1/image/cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/usr/share/man/man8/check_lft_balance.8
> CMake Error at infiniband-diags/man/cmake_install.cmake:66 (file):
> file INSTALL cannot find
> "/cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/var/tmp/portage/sys-cluster/rdma-core-37.1/work/rdma-core-37.1/buildlib/pandoc-prebuilt/8db9dce39d3eaf2d3992fd9198060d4bdfeb83d6":
> No such file or directory.
> Call Stack (most recent call first):
> cmake_install.cmake:222 (include)
>
> FAILED: CMakeFiles/install.util
> cd /cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/var/tmp/portage/sys-cluster/rdma-core-37.1/work/rdma-core-37.1_build
> && /cvmfs/pilot.eessi-hpc.org/2021.06/compat/linux/x86_64/usr/bin/cmake -P
> cmake_install.cmake
> ninja: build stopped: subcommand failed.
>
> Though the directory does exist and contains a bunch of files, this one is
> indeed missing. Is this expected (does it only work for certain cases?), or
> is something missing in this tarball?
It is definitely a bug.
Thanks
>
> Best regards,
> Bob Dröge
next prev parent reply other threads:[~2021-11-18 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 17:09 Installation with prebuilt docs failing Bob Dröge
2021-11-18 19:14 ` Leon Romanovsky [this message]
2021-11-19 13:34 ` 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=YZamDj1EqThLccyj@unreal \
--to=leon@kernel.org \
--cc=NMoreyChaisemartin@suse.de \
--cc=b.e.droge@rug.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox