Skip to content
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

Compilation problem #102

Open
morsmordreb opened this issue Feb 22, 2024 · 1 comment
Open

Compilation problem #102

morsmordreb opened this issue Feb 22, 2024 · 1 comment

Comments

@morsmordreb
Copy link

How can I know the relationship between the current tag of our project and the cuda version? There are many errors when compiling. For example, I am currently using CUDA-12.0, corresponding to the project 12.0-0, there will be such errors:

expected ‘nvmlDevice_t’ {aka ‘struct ’} but argument is of type ‘struct nvmlDevice_st *’
nvmlReturn_t DECLDIR nvmlVgpuTypeGetMaxInstances(nvmlDevice_t device, nvmlVgpuTypeId_t vgpuTypeId, unsigned int *vgpuInstanceCount);

Here's what makfie wrote
CGO_CFLAGS = -i/usr/local/cuda - 12.0 / include
CGO_LDFLAGS="-L /usr/local/cuda-12.0/lib64-lnvidia-ml"

@elezar
Copy link
Member

elezar commented Apr 4, 2024

@morsmordreb you should be able to use newer bindings against older CUDA versions since we detect the versioned APIs automatically. (There may be some edge cases that are not covered, but we can address those if reported).

It is even possible to use older bindings against newer CUDA versions -- with the caveat that any functions added since then will not be available.

With this in mind, I don't think it's required to provide your own nvml.h to build applications that use this package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants