Displaying 2 results from an estimated 2 matches for "tmp4af7576aa6b5441391fa4aea101d878d".
2015 Jun 09
2
[LLVMdev] msbuild and clang
...64-temp-Release\kill_python\\"
/Fd"C:\Python-2.7.10\PCbuild\x64-temp-Release\kill_python\vc120.pdb" /Gd
/TC /errorReport:queue /USECL:MS_OPTERON /GS- kill_python.c
TRACKER : error TRK0002: Failed to execute command:
"C:\Python-2.7.10\PCbuild\CL.exe
@C:\Users\w\AppData\Local\Temp\tmp4af7576aa6b5441391fa4aea101d878d.rsp".
The operation identifier is not valid.
[C:\Python-2.7.10\PCbuild\kill_python.vcxproj]
I'm not quite sure what to make of this, but a Google search for 'the
operation identifier is not valid' turned up this:
https://connect.microsoft.com/VisualStudio/feedback/details/714228/...
2015 Jun 08
3
[LLVMdev] msbuild and clang
I'm trying to compile some large programs with clang on Windows (with a
view to compiling to bit code and then running some whole program
optimisations on the bit code).
Take for example the Python 2.7 interpreter:
As is typically the case, the usual build procedure involves running
msbuild which invokes the Microsoft compiler.
The most obvious procedure would then be to substitute