[SERVER-67152] MongoDB failed to build suites with MSVC on windows arm64EC Created: 09/Jun/22  Updated: 29/Sep/22  Resolved: 20/Sep/22

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Yang Shino Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

VS 2019 + Windows Server 2019 + MongoDB master branch latest revision


Attachments: Text File MongoDB_build_arm64ec.log     Text File config.log    
Operating System: ALL
Steps To Reproduce:
  1. set VSCMD_SKIP_SENDTELEMETRY=1 & "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\Tools\VsDevCmd.bat" -host_arch=amd64 -arch=arm64
  2. git clone https://github.com/mongodb/mongo F:\mongo
  3. cd F:\mongo
  4. pip3 install -r etc/pip/compile-requirements.txt
  5. python.exe -m pip install evergreen.py
  6. set CL=/arm64EC
  7. Python buildscripts/scons.py install-all -j4

Error info:

Checking if C++ compiler "$CC" is MSVC... no
Checking if C++ compiler "$CC" is clang... no
Checking if C++ compiler "$CC" is GCC... no
Couldn't identify the C++ compiler
See F:\mongo\build\scons\config.log for details

Participants:

 Description   

MongoDB failed to build suites with MSVC on windows arm64EC. It can be reproduced on master latest revision. Could you help have a look about this issue? Thanks in advance!



 Comments   
Comment by Edwin Zhou [ 20/Sep/22 ]

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Edwin Zhou [ 07/Sep/22 ]

Hi shinoyang147@gmail.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please attempt building this on a stable release?

Best,
Edwin

Comment by Edwin Zhou [ 17/Aug/22 ]

Hi shinoyang147@gmail.com,

Thank you for your report and your patience while I investigate this issue. It appears that cl isn't being recognized in your PATH as the C++ compiler, despite appearing discovered in your PATH as shown in the build log:

cl /Fobuild\scons\opt\sconf_temp\conftest_4f0e9b4472e273623d18770138ab2253_0_c0baa25ae9368342c1d6e49bc8dd7e86.obj /c build\scons\opt\sconf_temp\conftest_4f0e9b4472e273623d18770138ab2253_0.cpp /TP /nologo
'cl' is not recognized as an internal or external command,
 
cl found in $PATH at C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\ARM64\cl.EXE
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\ARM64\cl.EXE resolves to C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\Hostx64\arm64\cl.exe

However, given that this attempt is on the master branch which is susceptible to changes that make affect the build process, could you attempt this on a stable release?

Best,
Edwin

Comment by Yang Shino [ 09/Jun/22 ]

The SDK version used by arm64ec have been included

Run "set include" display 

Run "set INCLUDE" Run "set lib"
INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\ATLMFC\include;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\include;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\cppwinrt;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\ATLMFC\include;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\include;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.22618.0\cppwinrt LIB=C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\ARM64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.22618.0\ucrt\arm64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.22618.0\um\arm64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\ATLMFC\lib\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.22618.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.22618.0\um\x64
LIBPATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\ARM64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\x86\store\references;C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.22618.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.22618.0;C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\ATLMFC\lib\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\x64;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\lib\x86\store\references;C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.22618.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.22618.0;C:\Windows\Microsoft.NET\Framework64\v4.0.30319
Generated at Thu Feb 08 06:07:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.