kou commented on PR #12749:
URL: https://github.com/apache/arrow/pull/12749#issuecomment-1100388959

   @lidavidm It seems that this breaks CI on macOS:
   
   
https://github.com/ursacomputing/crossbow/runs/6038992284?check_suite_focus=true#step:6:5601
   
   ```text
   [ 64%] Building CXX object 
src/arrow/flight/CMakeFiles/arrow_flight_testing_objlib.dir/test_definitions.cc.o
   
/Users/runner/work/crossbow/crossbow/arrow/cpp/src/arrow/flight/test_definitions.cc:1370:45:
 error: constexpr variable cannot have non-literal type 'const 
std::initializer_list<StatusCode>'
   constexpr std::initializer_list<StatusCode> kStatusCodes = {
                                               ^
   
/Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/initializer_list:58:28:
 note: 'initializer_list<arrow::StatusCode>' is not literal because it is not 
an aggregate and has no constexpr constructors other than copy or move 
constructors
   class _LIBCPP_TEMPLATE_VIS initializer_list
                              ^
   
/Users/runner/work/crossbow/crossbow/arrow/cpp/src/arrow/flight/test_definitions.cc:1389:51:
 error: constexpr variable cannot have non-literal type 'const 
std::initializer_list<FlightStatusCode>'
   constexpr std::initializer_list<FlightStatusCode> kFlightStatusCodes = {
                                                     ^
   
/Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/initializer_list:58:28:
 note: 'initializer_list<arrow::flight::FlightStatusCode>' is not literal 
because it is not an aggregate and has no constexpr constructors other than 
copy or move constructors
   class _LIBCPP_TEMPLATE_VIS initializer_list
                              ^
   2 errors generated.
   ```
   
   Could you confirm this?


-- 
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