kou opened a new issue, #41509:
URL: https://github.com/apache/arrow/issues/41509

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/49736306#L1461
   
   ```text
   FAILED: 
src/arrow/CMakeFiles/arrow_integration_shared.dir/Unity/unity_0_cxx.cxx.obj 
   C:\Miniconda38-x64\envs\arrow\Library\bin\ccache.exe 
C:\PROGRA~2\MICROS~1\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\cl.exe
  /nologo /TP -DARROW_EXPORTING -DARROW_HAVE_RUNTIME_AVX2 
-DARROW_HAVE_RUNTIME_AVX512 -DARROW_HAVE_RUNTIME_BMI2 
-DARROW_HAVE_RUNTIME_SSE4_2 -DARROW_HAVE_SSE4_2 -DPROTOBUF_USE_DLLS 
-DUSE_IMPORT_EXPORT -D_CRT_SECURE_NO_WARNINGS 
-D_ENABLE_EXTENDED_ALIGNED_STORAGE -IC:\projects\arrow\cpp\build\src 
-IC:\projects\arrow\cpp\src -IC:\projects\arrow\cpp\src\generated 
-external:IC:\Miniconda38-x64\envs\arrow\Library\include\rapidjson -external:W0 
/DWIN32 /D_WINDOWS /GR /EHsc /D_SILENCE_TR1_NAMESPACE_DEPRECATION_WARNING  
/EHsc /wd5105 /bigobj /utf-8 /W3 /wd4800 /wd4996 /wd4065  /WX /MP /MD /Od 
/UNDEBUG -std:c++17 -MD /showIncludes 
/Fosrc\arrow\CMakeFiles\arrow_integration_shared.dir\Unity\unity_0_cxx.cxx.obj 
/Fdsrc\arrow\CMakeFiles\arrow_integration_shared.dir\ /FS -c 
C:\projects\arrow\cpp\build\src\arrow\CMakeFiles\arrow_integration_shared.dir\Unity\unity_0_
 cxx.cxx
   C:\projects\arrow\cpp\src\arrow/integration/json_internal.h(26): fatal error 
C1083: Cannot open include file: 'rapidjson/document.h': No such file or 
directory
   [37/451] Building CXX object 
src\arrow\CMakeFiles\arrow_csv_shared.dir\Unity\unity_0_cxx.cxx.obj
   ninja: build stopped: subcommand failed.
   ```
   
   ### Component(s)
   
   C++, Continuous Integration


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to