View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0013674

CMake

public

2012-11-09 13:19

2016-06-10 14:31

Reporter

James Shackleford

Assigned To

Kitware Robot

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

moved

Platform

Linux

Ubuntu

OS Version

12.04 LTS

Product Version

CMake 2.8.10.1

Target Version

Fixed in Version

Summary

0013674: FindCUDA does not respect -ccbin or --compiler-bindir arguments

Description

FindCUDA/run_nvcc.cmake (lines 106--115) prevent manual specification of the compiler to be used by the Nvidia CUDA compiler nvcc via the -ccbin or --compiler-bindir arguments. The issue is to due the incorrect usage of LIST(FIND ...) to perform a substring search, resulting in a false negative.

As a result of the failed LIST(FIND ...), run_nvcc.cmake sets the preferred compiler to the system default gcc *AND* also passes the undetected manually specified gcc version. This results in nvcc failing due to a duplicate parameter specification for the external compiler.

Because nvcc is only compatible with a select few versions of gcc on Linux, the inability to set this parameter is an issue for users who do not use one of these Nvidia approved versions of gcc as their default compiler.

Steps To Reproduce

For example:

set (CUDA_NVCC_FLAGS "${CUDA_NVCC_FLAGS} --compiler-bindir=/usr/bin/gcc-4.4")

with result in

nvcc fatal : redefinition of argument 'compiler-bindir'

Additional Information

I do not believe FindCUDA/run_nvcc.cmake (lines 106--115) are necessary. Removal of these offending lines seems to restore correct behavior for the cases:

[1] -ccbin parameter not specified
[2] -ccbin parameter specified
[3] --compiler-bindir parameter not specified
[4] --compiler-bindir parameter specified

Tags

CMake, CUDA, FindCUDA, nvcc

Attached Files

FindCUDA.patch [^] (802 bytes) 2012-11-09 13:19 [Show Content] [Hide Content]

--- Modules/FindCUDA/run_nvcc.cmake	2012-11-06 14:41:36.000000000 -0500
+++ Modules/FindCUDA/run_nvcc_fix.cmake	2012-11-09 12:34:33.869545694 -0500
@@ -103,16 +103,6 @@
 # Add the build specific configuration flags
 list(APPEND CUDA_NVCC_FLAGS ${CUDA_NVCC_FLAGS_${build_configuration}})
 
-# Any -ccbin existing in CUDA_NVCC_FLAGS gets highest priority
-list( FIND CUDA_NVCC_FLAGS "-ccbin" ccbin_found0 )
-list( FIND CUDA_NVCC_FLAGS "--compiler-bindir" ccbin_found1 )
-if( ccbin_found0 LESS 0 AND ccbin_found1 LESS 0 )
-  if (CUDA_HOST_COMPILER STREQUAL "$(VCInstallDir)bin" AND DEFINED CCBIN)
-    set(CCBIN -ccbin "${CCBIN}")
-  else()
-    set(CCBIN -ccbin "${CUDA_HOST_COMPILER}")
-  endif()
-endif()
 
 # cuda_execute_process - Executes a command with optional command echo and status message.
 #

Relationships

Notes
(0031522) James Bigler (developer) 2012-11-11 00:22	What happens when you remove the equal sign? And by the way CUDA_NVCC_FLAGS is a list and not a string like the CMAKE_C_FLAGS and CMAKE_CXX_FLAGS variables. You should probably do something like: list (APPEND CUDA_NVCC_FLAGS --compiler-bindir /usr/bin/gcc-4.4) I might need to fix up the flag detection to accomodate for using the equal sign, but I want you to be able to make progress as well. Alternatively with this version of FindCUDA you can now specify the host compiler to use directly: # CUDA_HOST_COMPILER (Default CMAKE_C_COMPILER, $(VCInstallDir)/bin for VS) # -- Set the host compiler to be used by nvcc. Ignored if -ccbin or # --compiler-bindir is already present in the CUDA_NVCC_FLAGS or # CUDA_NVCC_FLAGS_<CONFIG> variables. For Visual Studio targets # $(VCInstallDir)/bin is a special value that expands out to the path when # the command is run from withing VS. #

(0033748) domibel (reporter) 2013-08-26 15:14	Removing the equal sign helped in my case.

(0038884) Michele Mastropietro (reporter) 2015-06-04 11:09	Please see http://stackoverflow.com/questions/30642229/fail-to-build-shared-library-using-cmake-and-cuda [^] For me the double `--ccbin` option inclusion is resolved with the patch attached.

(0042147) Kitware Robot (administrator) 2016-06-10 14:28	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2012-11-09 13:19	James Shackleford	New Issue
2012-11-09 13:19	James Shackleford	File Added: FindCUDA.patch
2012-11-09 13:21	James Shackleford	Tag Attached: CMake
2012-11-09 13:21	James Shackleford	Tag Attached: CUDA
2012-11-09 13:22	James Shackleford	Tag Attached: FindCUDA
2012-11-09 13:22	James Shackleford	Tag Attached: nvcc
2012-11-11 00:22	James Bigler	Note Added: 0031522
2013-08-26 15:14	domibel	Note Added: 0033748
2015-06-04 11:09	Michele Mastropietro	Note Added: 0038884
2016-06-10 14:28	Kitware Robot	Note Added: 0042147
2016-06-10 14:28	Kitware Robot	Status	new => resolved
2016-06-10 14:28	Kitware Robot	Resolution	open => moved
2016-06-10 14:28	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed