guanxingithub opened a new issue #20863:
URL: https://github.com/apache/incubator-mxnet/issues/20863


   ## Description
   We would like to report a compilation issue on the master branch, related to 
use of NVIDIA’s NVML library.  The source lines involved are: 
https://github.com/apache/incubator-mxnet/blob/master/src/profiler/storage_profiler.cc#L103-L111
   
   These were the same lines that caused issue#20145, as was fixed by @Zha0q1 
in  PR#20146.  The problem is that these source lines still have a sensitivity 
to the driver version and cmake build flag NVML_NO_UNVERSIONED_FUNC_DEFS.
   
   ### Error Message
   This issue was found when we compile MXNet master on the cuda11 450.x 
driver, where we see:
   
   FAILED:
   
   
CMakeFiles/mxnet.dir/src/profiler/storage_profiler.cc.o../src/profiler/storage_profiler.cc:109:78:
 error: cannot convert ‘nvmlProcessInfo_st*’ to ‘nvmlProcessInfo_v1_t*’ {aka 
‘nvmlProcessInfo_v1_st*’}
     109 |     nvmlDeviceGetComputeRunningProcesses(nvml_device, &info_count, 
infos.data());
   
   In file included from ../src/profiler/storage_profiler.cc:22:
   /usr/local/cuda/include/nvml.h:8403:127: note:   initializing argument 3 of 
‘nvmlReturn_t nvmlDeviceGetComputeRunningProcesses(nvmlDevice_t, unsigned int*, 
nvmlProcessInfo_v1_t*)’
    8403 | nvmlReturn_t DECLDIR 
nvmlDeviceGetComputeRunningProcesses(nvmlDevice_t device, unsigned int 
*infoCount, nvmlProcessInfo_v1_t *infos);
   
   
   ### Steps to reproduce
   1. Find machine with cuda11 450.x driver
   2. Compile mxnet
   
   ## What have you tried to solve it?
   
   1. This issue was found and fixed by Dick Carter
   2. @DickJC123 has developed a general solution that avoids compilation 
errors no matter which signature of the nvmlDeviceGetComputeRunningProcesses() 
function is enabled in the code. We will be submitting this fix as a PR shortly.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to