StefanLobbenmeierObjego commented on issue #43235:
URL: https://github.com/apache/arrow/issues/43235#issuecomment-2295976590

   Had the same error with macOS 14.6.1 (23G93) on Apple M1
   
   Installing pyarrow via homebrew resolved that error, but the build still 
failed with 
   
   ```
         [72/151] Compiling C object 
pandas/_libs/pandas_datetime.cpython-312-darwin.so.p/src_vendored_numpy_datetime_np_datetime.c.o
         FAILED: 
pandas/_libs/pandas_datetime.cpython-312-darwin.so.p/src_vendored_numpy_datetime_np_datetime.c.o
         cc -Ipandas/_libs/pandas_datetime.cpython-312-darwin.so.p 
-Ipandas/_libs -I../../pandas/_libs 
-I../../../../pip-build-env-un8ydyqn/overlay/lib/python3.12/site-packages/numpy/_core/include
 -I../../pandas/_libs/include 
-I/opt/homebrew/opt/[email protected]/Frameworks/Python.framework/Versions/3.12/include/python3.12
 -fvisibility=hidden -fcolor-diagnostics -DNDEBUG -Wall -Winvalid-pch -std=c99 
-O3 -DNPY_NO_DEPRECATED_API=0 -DNPY_TARGET_VERSION=NPY_1_21_API_VERSION -MD -MQ 
pandas/_libs/pandas_datetime.cpython-312-darwin.so.p/src_vendored_numpy_datetime_np_datetime.c.o
 -MF 
pandas/_libs/pandas_datetime.cpython-312-darwin.so.p/src_vendored_numpy_datetime_np_datetime.c.o.d
 -o 
pandas/_libs/pandas_datetime.cpython-312-darwin.so.p/src_vendored_numpy_datetime_np_datetime.c.o
 -c ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c
         ../../pandas/_libs/src/vendored/numpy/datetime/np_datetime.c:946:54: 
error: no member named 'c_metadata' in 'struct _PyArray_Descr'
             return (((PyArray_DatetimeDTypeMetaData 
*)dtype->c_metadata)->meta);
                                                       ~~~~~  ^
         1 error generated.
   ```
   
   I suspect it still needs to be exactly the same version in brew and pip or 
something like that


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