You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mxnet.apache.org by "Kellen Sunderland (JIRA)" <ji...@apache.org> on 2018/04/16 20:07:00 UTC

[jira] [Created] (MXNET-324) Use default nvcc when configured nvcc not present.

Kellen Sunderland created MXNET-324:
---------------------------------------

             Summary: Use default nvcc when configured nvcc not present.
                 Key: MXNET-324
                 URL: https://issues.apache.org/jira/browse/MXNET-324
             Project: Apache MXNet
          Issue Type: Bug
            Reporter: Kellen Sunderland


This fixes an issue with the nvcc path resolution logic in the Makefile ([#10553|https://github.com/apache/incubator-mxnet/issues/10553]).  In prior releases the makefile would use $(USE_CUDA_PATH)/bin/nvcc for nvcc no matter what was specified in config. For some users this was actually a good thing if 'nvcc' was not on the path, as it would specify the binary with an absolute path.  However the behaviour in the prior release caused issues when cross compiling. You may have an arm and x86 cuda path specified, and you need to select the correct nvcc for your platform.

This PR checks the configured nvcc to ensure it is actually on the path.  If it isn't it will set the binary to the absolute path.  This should match the behaviour of the prior release for users without nvcc on the path, and also allow for cross-compilation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@mxnet.apache.org
For additional commands, e-mail: issues-help@mxnet.apache.org