Okay, so trying a straight compile of the Python interpreter with clang-cl, I used the following commands: cd \python-2.7.10\pcbuild copy C:\llvm\build\Release\bin\clang-cl.exe cl.exe rd /q /s amd64 rd /q /s win32-temp-debug rd /q /s win32-temp-release rd /q /s x64-temp-debug rd /q /s x64-temp-release msbuild /p:Configuration=Release /v:diag /fileLogger pcbuild.sln (The second line is the one that substitutes clang-cl - with that removed, everything is successful) The build failed with the following error message: Tracking command: C:\Program Files (x86)\MSBuild\12.0\bin\Tracker.exe /d "C:\Program Files (x86)\MSBuild\12.0\bin\FileTracker.dll" /i C:\Python-2.7.10\PCbuild\x64-temp-Release\kill_python\kill_python.tlog /r C:\PYTHON-2.7.10\PCBUILD\KILL_PYTHON.C /b MSBuildConsole_CancelEvent306536dcec844c0c97517539ced8ed5d /c C:\Python-2.7.10\PCbuild\CL.exe /c /I..\Include /I..\PC /Zi /nologo /W3 /WX- /O2 /Ob1 /Oi /GL /D _WIN64 /D _M_X64 /D NDEBUG /D _WIN32 /GF /Gm- /MT /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Fo"C:\Python-2.7.10\PCbuild\x64-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/visual-studio-11-various-problems-caused-by-its-use-of-3-bit-compiler-even-when-installed-on-64-bit-windows Which is not actually the same thing, but suggests that error message is msbuild's way of saying something in the toolchain is incompatible with something else. Any idea what's wrong here? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150609/10b01e65/attachment.html>
We haven't hit this yet. Can you disable tracker.exe? There's some XML attribute you can flip for it. On Tue, Jun 9, 2015 at 6:10 AM, Russell Wallace <russell.wallace at gmail.com> wrote:> Okay, so trying a straight compile of the Python interpreter with > clang-cl, I used the following commands: > > cd \python-2.7.10\pcbuild > copy C:\llvm\build\Release\bin\clang-cl.exe cl.exe > rd /q /s amd64 > rd /q /s win32-temp-debug > rd /q /s win32-temp-release > rd /q /s x64-temp-debug > rd /q /s x64-temp-release > msbuild /p:Configuration=Release /v:diag /fileLogger pcbuild.sln > > (The second line is the one that substitutes clang-cl - with that removed, > everything is successful) > > The build failed with the following error message: > > Tracking command: > C:\Program Files (x86)\MSBuild\12.0\bin\Tracker.exe /d "C:\Program Files > (x86)\MSBuild\12.0\bin\FileTracker.dll" /i > C:\Python-2.7.10\PCbuild\x64-temp-Release\kill_python\kill_python.tlog /r > C:\PYTHON-2.7.10\PCBUILD\KILL_PYTHON.C /b > MSBuildConsole_CancelEvent306536dcec844c0c97517539ced8ed5d /c > C:\Python-2.7.10\PCbuild\CL.exe /c /I..\Include /I..\PC /Zi /nologo /W3 > /WX- /O2 /Ob1 /Oi /GL /D _WIN64 /D _M_X64 /D NDEBUG /D _WIN32 /GF /Gm- /MT > /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope > /Fo"C:\Python-2.7.10\PCbuild\x64-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/visual-studio-11-various-problems-caused-by-its-use-of-3-bit-compiler-even-when-installed-on-64-bit-windows > <https://urldefense.proofpoint.com/v2/url?u=https-3A__connect.microsoft.com_VisualStudio_feedback_details_714228_visual-2Dstudio-2D11-2Dvarious-2Dproblems-2Dcaused-2Dby-2Dits-2Duse-2Dof-2D3-2Dbit-2Dcompiler-2Deven-2Dwhen-2Dinstalled-2Don-2D64-2Dbit-2Dwindows&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=CtdVIyKfDBlVrIG8rllj8yHGq4c4BsN3lvESbm_CjkQ&s=o4KItqcMr3rNupr7M4SBgnY2NU162F8So8wh7hdqptk&e=> > > Which is not actually the same thing, but suggests that error message is > msbuild's way of saying something in the toolchain is incompatible with > something else. Any idea what's wrong here? > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150609/912bf45a/attachment.html>
Right, tracker can be disabled with /p:TrackFileAccess=false and that gets over that hurdle. It's now failing with fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86' I'm trying to specify 64-bit across the board; in particular, I'm using 64-bit clang, I have the environment variable set Platform=X64 and the argument /p:Platform="x64" to msbuild. Any idea why it's still talking about a 32-bit target machine type? The build with the Microsoft compiler was successfully 64-bit even without those options explicitly set. On Tue, Jun 9, 2015 at 5:38 PM, Reid Kleckner <rnk at google.com> wrote:> We haven't hit this yet. Can you disable tracker.exe? There's some XML > attribute you can flip for it. > > On Tue, Jun 9, 2015 at 6:10 AM, Russell Wallace <russell.wallace at gmail.com > > wrote: > >> Okay, so trying a straight compile of the Python interpreter with >> clang-cl, I used the following commands: >> >> cd \python-2.7.10\pcbuild >> copy C:\llvm\build\Release\bin\clang-cl.exe cl.exe >> rd /q /s amd64 >> rd /q /s win32-temp-debug >> rd /q /s win32-temp-release >> rd /q /s x64-temp-debug >> rd /q /s x64-temp-release >> msbuild /p:Configuration=Release /v:diag /fileLogger pcbuild.sln >> >> (The second line is the one that substitutes clang-cl - with that >> removed, everything is successful) >> >> The build failed with the following error message: >> >> Tracking command: >> C:\Program Files (x86)\MSBuild\12.0\bin\Tracker.exe /d "C:\Program >> Files (x86)\MSBuild\12.0\bin\FileTracker.dll" /i >> C:\Python-2.7.10\PCbuild\x64-temp-Release\kill_python\kill_python.tlog /r >> C:\PYTHON-2.7.10\PCBUILD\KILL_PYTHON.C /b >> MSBuildConsole_CancelEvent306536dcec844c0c97517539ced8ed5d /c >> C:\Python-2.7.10\PCbuild\CL.exe /c /I..\Include /I..\PC /Zi /nologo /W3 >> /WX- /O2 /Ob1 /Oi /GL /D _WIN64 /D _M_X64 /D NDEBUG /D _WIN32 /GF /Gm- /MT >> /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope >> /Fo"C:\Python-2.7.10\PCbuild\x64-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/visual-studio-11-various-problems-caused-by-its-use-of-3-bit-compiler-even-when-installed-on-64-bit-windows >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__connect.microsoft.com_VisualStudio_feedback_details_714228_visual-2Dstudio-2D11-2Dvarious-2Dproblems-2Dcaused-2Dby-2Dits-2Duse-2Dof-2D3-2Dbit-2Dcompiler-2Deven-2Dwhen-2Dinstalled-2Don-2D64-2Dbit-2Dwindows&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=CtdVIyKfDBlVrIG8rllj8yHGq4c4BsN3lvESbm_CjkQ&s=o4KItqcMr3rNupr7M4SBgnY2NU162F8So8wh7hdqptk&e=> >> >> Which is not actually the same thing, but suggests that error message is >> msbuild's way of saying something in the toolchain is incompatible with >> something else. Any idea what's wrong here? >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150610/cb144b69/attachment.html>