Karen Huang created MESOS-7209:
----------------------------------

             Summary: Mesos failed to build due to error MSB6006: "cmd.exe" 
exited with code 255 on windows
                 Key: MESOS-7209
                 URL: https://issues.apache.org/jira/browse/MESOS-7209
             Project: Mesos
          Issue Type: Bug
         Environment: Windows 10 (64bit) + VS2015 Update 3
            Reporter: Karen Huang


I try to build mesos with Debug|x64 configuration on Windows. It failed to 
build due to error MSB6006: "cmd.exe" exited with code 
255.[F:\mesos\build_x64\ensure_tool_arch.vcxproj]. This error is reported when 
build ensure_tool_arch.vcxproj project.

Here is repro steps:
1. git clone -c core.autocrlf=true https://github.com/apache/mesos F:\mesos\src
2. Open a VS amd64 command prompt as admin and browse to F:\mesos\src
3. .\bootstrap.bat
4. cmake ..\src -G "Visual Studio 14 2015 Win64" -DENABLE_LIBEVENT=1 
-DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin"
5. msbuild Mesos.sln /p:Configuration=Debug /p:PreferredToolArchitecture=x64 /m 
/t:Rebuild

Error message:
 CustomBuild:
         Building Custom Rule F:/mesos/src/CMakeLists.txt
         CMake does not need to re-run because 
F:\mesos\build_x64\CMakeFiles\generate.stamp is up-to-date.
         ( was unexpected at this time.
    43>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error 
MSB6006: "cmd.exe" exited with code 255. 
[F:\mesos\build_x64\ensure_tool_arch.vcxproj]

If you build the project ensure_tool_arch.vcxproj in VS IDE seperatly. The 
error info is as bleow:
2>------ Rebuild All started: Project: ensure_tool_arch, Configuration: Debug 
x64 ------
2>  Building Custom Rule D:/Mesos/src/CMakeLists.txt
2>  CMake does not need to re-run because 
D:\Mesos\build_x64\CMakeFiles\generate.stamp is up-to-date.
2>  ( was unexpected at this time.
2>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error 
MSB6006: "cmd.exe" exited with code 255.






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to