-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./configure problem caused by infiniband/driver.h #50
Comments
Can you send the contents of |
of cause |
The rdma-core 18 build depends on many more kernel headers than rdma-core 17. Fix the CCAN includes from the rdma-core 18 headers because the directory structure in rdma-core was modified, whereas we keep a more vanilla layout. Add all of the userspace ABI kernel headers to the source tree so we can build against the newer rdma-core version. The updated build has been tested on my local system against rdma-core 17 and 18 and appears to work correctly. Signed-off-by: Patrick MacArthur <[email protected]>
PR #51 should fix the build for rdma-core 18. Unfortunately, we must rely on internal rdma-core headers because rdma-core does not support out-of-tree drivers. |
Hi Debe, How did you install rdma-core 17+? |
I've a problem configuring urdma. I tried with rdma-core versions 20.1, 19.1, 18.2 and 17.3. I've checked the debian package rules and indeed the infiniband/driver.h is missing in all of them.
Is this header really needed or only for the parameter checking inside configure script?
Otherwise I'd suggest to remove driver.h as it's been marked internal.
…
checking for Linux kernel source tree... /lib/modules/4.17.0-0.bpo.1-amd64/build
checking for library containing verbs_register_driver_18... no
checking for library containing verbs_register_driver_17... -libverbs
checking number of arguments verbs_init_and_alloc_context takes... no
configure: error: Colud not determine; check your rdma-core installation
…
The text was updated successfully, but these errors were encountered: