[ 
https://issues.apache.org/jira/browse/MESOS-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099280#comment-16099280
 ] 

Michael Park commented on MESOS-7794:
-------------------------------------

{noformat}
commit 2215600f4ba86afbe510cf96d3ff518b8602e43f
Author: Andrew Schwartzmeyer <[email protected]>
Date:   Mon Jul 24 16:37:42 2017 -0700

    Windows: Disabled permissive building.

    This flag enables warnings for non-standards conformant code.

    https://blogs.msdn.microsoft.com/vcblog/2016/11/16/permissive-switch/

    Review: https://reviews.apache.org/r/61093/
{noformat}

> Mesos failed with error c2102 when build in conformance mode (/permissive-)
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-7794
>                 URL: https://issues.apache.org/jira/browse/MESOS-7794
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: PhoebeHui
>            Assignee: Andrew Schwartzmeyer
>              Labels: stout, windows
>
> I try to build mesos with Debug|x64 configuration on Windows with VS2017.2
> 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. Set _CL_=/permissive-
> 4. bootstrap.bat
> 5. mkdir build_x64 && pushd build_x64
> 6. cmake ..\src -G "Visual Studio 15 2017 Win64" -DENABLE_LIBEVENT=1 
> -DHAS_AUTHENTICATION=0 -DPATCHEXE_PATH="C:\gnuwin32\bin -T host=x64"
> 7. msbuild Mesos.sln /p:Configuration=Debug /p:Platform=x64 /m /t:Rebuild
> Error message:
> D:\Mesos\src\3rdparty\stout\include\stout/os/windows/shell.hpp(355): error 
> C2102: '&' requires l-value (compiling source file 
> D:\Mesos\src\3rdparty\libprocess\src\time.cpp) 
> [D:\Mesos\build_x64\3rdparty\libprocess\src\process-0.0.1.vcxproj]
> Smaller repro code like this:
> void test(unsigned long *a){}
> int main()
> {
> int i;
> test(&static_cast<unsigned long>(i));
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to