mxnet-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kellen Sunderland (JIRA)" <>
Subject [jira] [Updated] (MXNET-324) Use default nvcc when configured nvcc not present.
Date Fri, 21 Sep 2018 15:57:00 GMT


Kellen Sunderland updated MXNET-324:
    Resolution: Fixed
        Status: Done  (was: To Do)

> Use default nvcc when configured nvcc not present.
> --------------------------------------------------
>                 Key: MXNET-324
>                 URL:
>             Project: Apache MXNet
>          Issue Type: Bug
>            Reporter: Kellen Sunderland
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
> This fixes an issue with the nvcc path resolution logic in the Makefile ([#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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message