From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"kheib@redhat.com" <kheib@redhat.com>,
"edwards@nvidia.com" <edwards@nvidia.com>
Subject: Re: [bug-report]rdma-core v51.0 build error with Rocky Linux 8.8
Date: Thu, 23 May 2024 12:19:02 -0300 [thread overview]
Message-ID: <20240523151902.GJ69273@ziepe.ca> (raw)
In-Reply-To: <SA1PR11MB68950882F65EE948009BF33986ED2@SA1PR11MB6895.namprd11.prod.outlook.com>
On Thu, May 16, 2024 at 07:48:06PM +0000, Marciniszyn, Mike wrote:
> Seen on Rocky Linux 8.8 with rdma-core v51.0.
>
> I suspect 8.9 shows the same issue and I know the RC for RHEL 8.10 does as well.
>
> The cmake version is 3.20.2.
>
> The linux kernel version and hardware is not relevant since this is a cmake/build issue.
>
> The hardware is also not relevant.
>
> To reproduce:
> 1. download an untar the v51.0 tar ball to ~
> cd ~
> wget https://github.com/linux-rdma/rdma-core/releases/download/v51.0/rdma-core-51.0.tar.gz
> tar -zxvf tar -zxvf rdma-core-51.0.tar.gz
> 2. create the following directories
> mkdir -p ~/rpmbuild/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS,OTHER}
> 3. copy the spec file
> cp cp rdma-core-51.0/redhat/rdma-core.spec ~/rpmbuild/SPECS
> 4. Create SOURCES
> tar -zcvf ~/rpmbuild/SOURCES/rdma-core-51.0.tar.gz rdma-core-51.0
> 5. load build dependencies
> ensure AppStream, BaseOS, PowerTools repos are accessible
> sudo dnf install -y dnf-plugins-core rpm-build
> cd ~/rpmbuild/SPECS
> sudo dnf builddep -y rdma-core.spec
> 6. Load an additional pythion interpreter
> sudo dnf install python39
> 6. do the build
> rpmbuild -ba rdma-core.spec
>
> The build gets the following errors:
> error: File not found: /home/mmarcini/rpmbuild/BUILDROOT/rdma-core-51.0-1.el8.x86_64/usr/lib64/python3.6/site-packages/pyverbs
> error: File not found: /home/mmarcini/rpmbuild/BUILDROOT/rdma-core-51.0-1.el8.x86_64/usr/share/doc/rdma-core/tests/*.py
>
>
> RPM build errors:
> File not found: /home/mmarcini/rpmbuild/BUILDROOT/rdma-core-51.0-1.el8.x86_64/usr/lib64/python3.6/site-packages/pyverbs
> File not found: /home/mmarcini/rpmbuild/BUILDROOT/rdma-core-51.0-1.el8.x86_64/usr/share/doc/rdma-core/tests/*.py
>
> Earlier in the build this is seen:
> -- Found Python: /usr/bin/python3.9 (found version "3.9.16") found components: Interpreter
> -- Could NOT find cython (missing: CYTHON_EXECUTABLE CYTHON_VERSION_STRING)
>
> The issue appears to have been introduced by:
> 1462a8737 build: Fix cmake warning
>
> cmake appears to find the 3.9 python despite having:
> -DPYTHON_EXECUTABLE:PATH=%{__python3}
I looked at this briefly but didn't guess what the issue really was?
Do you know more?
Jason
next prev parent reply other threads:[~2024-05-23 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 19:48 [bug-report]rdma-core v51.0 build error with Rocky Linux 8.8 Marciniszyn, Mike
2024-05-23 15:19 ` Jason Gunthorpe [this message]
2024-05-24 16:40 ` Marciniszyn, Mike
2024-05-24 16:57 ` Jason Gunthorpe
2024-05-24 18:01 ` Marciniszyn, Mike
2024-05-24 18:22 ` Jason Gunthorpe
2024-05-24 18:24 ` Marciniszyn, Mike
2024-05-29 18:50 ` Marciniszyn, Mike
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=20240523151902.GJ69273@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=edwards@nvidia.com \
--cc=kheib@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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