Makefile: Do not create an empty linker response file
Since commit v3.1.0-rc1~821^2 (Windows: Use response files to specify link libraries for GNU tools, 2014-03-04) we use a response file to pass possibly long linker flag lists to the GNU linker on Windows. On MinGW, this may cause gfortran to use a response file to pass some flags to its own internal invocation. This is okay except when we are parsing implicit link flags from the compiler ABI detection build. If gfortran uses a response file in that case then we may miss extracting some of the implicit link flags, such as -lgfortran. Fortunately, in the compiler ABI detection case we do not actually link to anything so the response file is empty. Work around this problem by simply not using a response file when the list of flags it is used to pass is empty (or just whitespace). Reported-by: Bill Somerville <bill@classdesign.com>
This commit is contained in:
parent
433c6d4689
commit
1c5be1f367
|
@ -1846,7 +1846,7 @@ cmMakefileTargetGenerator
|
|||
useWatcomQuote);
|
||||
linkLibs = frameworkPath + linkPath + linkLibs;
|
||||
|
||||
if(useResponseFile)
|
||||
if(useResponseFile && linkLibs.find_first_not_of(" ") != linkLibs.npos)
|
||||
{
|
||||
// Lookup the response file reference flag.
|
||||
std::string responseFlagVar = "CMAKE_";
|
||||
|
|
Loading…
Reference in New Issue