You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "LinGao (JIRA)" <ji...@apache.org> on 2019/07/16 08:30:00 UTC

[jira] [Created] (MESOS-9894) Mesos failed to build due to fatal error C1083 on Windows using MSVC.

LinGao created MESOS-9894:
-----------------------------

             Summary: Mesos failed to build due to fatal error C1083 on Windows using MSVC.
                 Key: MESOS-9894
                 URL: https://issues.apache.org/jira/browse/MESOS-9894
             Project: Mesos
          Issue Type: Bug
          Components: build
         Environment: VS 2017 + Windows Server 2016
            Reporter: LinGao
         Attachments: log_x64_build.log

Mesos failed to build due to fatal error C1083: Cannot open include file: 'slave/volume_gid_manager/state.pb.h': No such file or directory on Windows using MSVC. It can be first reproduced on 6a026e3 reversion on master branch. Could you please take a look at this isssue? Thanks a lot!

Reproduce steps:

1. git clone -c core.autocrlf=true https://github.com/apache/mesos D:\mesos\src
2. Open a VS 2017 x64 command prompt as admin and browse to D:\mesos
3. cd src
4. .\bootstrap.bat
5. cd ..
6. mkdir build_x64 && pushd build_x64
7. cmake ..\src -G "Visual Studio 15 2017 Win64" -DCMAKE_SYSTEM_VERSION=10.0.17134.0 -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin" -T host=x64
8. msbuild Mesos.sln /p:Configuration=Debug /p:Platform=x64 /maxcpucount:4 /t:Rebuild

 

ErrorMessage:

D:\Mesos\src\include\mesos/docker/spec.hpp(29): fatal error C1083: Cannot open include file: 'mesos/docker/spec.pb.h': No such file or directory

D:\Mesos\src\src\slave/volume_gid_manager/state.hpp(21): fatal error C1083: Cannot open include file: 'slave/volume_gid_manager/state.pb.h': No such file or directory

D:\Mesos\src\src\slave/volume_gid_manager/state.hpp(21): fatal error C1083: Cannot open include file: 'slave/volume_gid_manager/state.pb.h': No such file or directory

 

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)