Closed asfimport closed 5 years ago
Uwe Korn / @xhochy:
[~hayesgb]
It seems that you are no on latest master. I would recommend pulling the sources again as we have made a lot of changes to the build system in the last days. They might already help.
Otherwise, you seem to be inside a conda environment with the latest build settings. Here you should nowadays use the compilers that are provided by Anaconda. You can install them using the compilers
package from conda-forge: conda install -c conda-forge compilers
and then reactivate your conda environment. On OSX, this also requires that you have the 10.9 OSX SDK downloaded, e.g. to /opt/MacOSX10.9.sdk
and then set export CONDA_BUILD_SYSROOT=/opt/MacOSX10.9.sdk
before running a new build (delete your build directory to be safe that all new settings are picked up).
Can you upload also the config.log
produced by jemalloc if it fails again?
Gregory Hayes: Not sure how I ended up at that documentation, but thank you for pointing me in the right direction.
I created download from git, and re-created my conda environment. Initially, I got an error that LLVM v7 was not available, and manually installed LLVM-META using conda, which eliminated that error. I'm still getting jemalloc errors though. Log file shown below:
install: mkdir /Users/Greg/documents/repos/arrow/cpp/build/jemalloc_ep-prefix/src/jemalloc_ep/dist: File exists
make[3]: *** [install_include] Error 71
make[3]: *** Waiting for unfinished jobs....
/usr/bin/install -c -m 755 bin/jemalloc-config /Users/Greg/documents/repos/arrow/cpp/build/jemalloc_ep-prefix/src/jemalloc_ep/dist/bin
/usr/bin/install -c -m 755 bin/jemalloc.sh /Users/Greg/documents/repos/arrow/cpp/build/jemalloc_ep-prefix/src/jemalloc_ep/dist/bin
/usr/bin/install -c -m 755 bin/jeprof /Users/Greg/documents/repos/arrow/cpp/build/jemalloc_ep-prefix/src/jemalloc_ep/dist/bin
Uwe Korn / @xhochy: This seems like a race condition in the jemalloc build. Does it work when you delete /Users/Greg/documents/repos/arrow/cpp/build/jemalloc_ep-prefix/src/jemalloc_ep/dist and then build again?
Gregory Hayes: That worked to get me past the jemalloc error. Now I'm seeing an unable to locate gandiva library error, when I try to run setup.py. This happens even if I flag GANDIVA =OFF and set
export PYARROW_WITH_GANDIVA=0
Uwe Korn / @xhochy: Please always post the error, otherwise we are unable to see what the problem could be.
Gregory Hayes: The immediate error is:
-- Configuring incomplete, errors occurred!
See also "/Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeOutput.log".
See also "/Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeError.log".
error: command 'cmake' failed with exit status 1
Output of the CMakeError.log file is:
Performing C++ SOURCE FILE Test CXX_SUPPORTS_ALTIVEC failed with the following output:
Change Dir: /Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_706c2/fast
/Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_706c2.dir/build.make CMakeFiles/cmTC_706c2.dir/build
Building CXX object CMakeFiles/cmTC_706c2.dir/src.cxx.o
/Users/Greg/anaconda3/envs/pyarrow-dev/bin/x86_64-apple-darwin13.4.0-clang++ -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -std=c++14 -fmessage-length=0 -DCXX_SUPPORTS_ALTIVEC -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.9 -maltivec -o CMakeFiles/cmTC_706c2.dir/src.cxx.o -c /Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeTmp/src.cxx
clang-4.0: error: invalid argument '-faltivec' only allowed with 'ppc/ppc64/ppc64le'
make[1]: *** [CMakeFiles/cmTC_706c2.dir/src.cxx.o] Error 1
make: *** [cmTC_706c2/fast] Error 2
Source file was:
int main() { return 0; }
Performing C++ SOURCE FILE Test CXX_SUPPORTS_ARMCRC failed with the following output:
Change Dir: /Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_c6418/fast
/Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_c6418.dir/build.make CMakeFiles/cmTC_c6418.dir/build
Building CXX object CMakeFiles/cmTC_c6418.dir/src.cxx.o
/Users/Greg/anaconda3/envs/pyarrow-dev/bin/x86_64-apple-darwin13.4.0-clang++ -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -std=c++14 -fmessage-length=0 -DCXX_SUPPORTS_ARMCRC -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.9 -march=armv8-a+crc -o CMakeFiles/cmTC_c6418.dir/src.cxx.o -c /Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeTmp/src.cxx
error: unknown target CPU 'armv8-a+crc'
make[1]: *** [CMakeFiles/cmTC_c6418.dir/src.cxx.o] Error 1
make: *** [cmTC_c6418/fast] Error 2
Source file was:
int main() { return 0; }
Uwe Korn / @xhochy:
[~hayesgb]
The CMakeError.log
is fine, these are simply error where we test your system for features that it doesn't have. No need to worry about this. Configuring incomplete, errors occurred!
indicates that CMake had errors and should have displayed it somewhere in the command line output (CMake doesn't stop at errors).
Gregory Hayes: I was able to successfully build the and run setup.py. Interestingly enough, after getting cmake to run successfully, I ran into problems with setup.py. The error reported was:
Run Build Command(s):/usr/bin/make cmTC_deb6c/fast
/Library/Developer/CommandLineTools/usr/bin/make -f CMakeFiles/cmTC_deb6c.dir/build.make CMakeFiles/cmTC_deb6c.dir/build
Building C object CMakeFiles/cmTC_deb6c.dir/testCCompiler.c.o
/Users/Greg/anaconda3/envs/pyarrow-dev/bin/x86_64-apple-darwin13.4.0-clang -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.9 -o CMakeFiles/cmTC_deb6c.dir/testCCompiler.c.o -c /Users/Greg/Documents/repos/arrow/python/build/temp.macosx-10.9-x86_64-3.7/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTC_deb6c
/Users/Greg/anaconda3/envs/pyarrow-dev/bin/cmake -E cmake_link_script CMakeFiles/cmTC_deb6c.dir/link.txt --verbose=1
/Users/Greg/anaconda3/envs/pyarrow-dev/bin/x86_64-apple-darwin13.4.0-clang -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.9 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-pie -Wl,-headerpad_max_install_names -Wl,-dead_strip_dylibs CMakeFiles/cmTC_deb6c.dir/testCCompiler.c.o -o cmTC_deb6c
ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/lib/libSystem.tbd, file was built for unsupported file format ( 0x2D 0x2D 0x2D 0x20 0x21 0x74 0x61 0x70 0x69 0x2D 0x74 0x62 0x64 0x2D 0x76 0x33 ) which is not the architecture being linked (x86_64): /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/lib/libSystem.tbd
ld: dynamic main executables must link with libSystem.dylib for architecture x86_64
clang-4.0: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [cmTC_deb6c] Error 1
make: *** [cmTC_deb6c/fast] Error 2
Following this link suggests the issue is $CONDA_BUILD_SYSROOT needs to be set to the MacOS10.9 sdk, and that it should be set in conda_build_config.yaml, but I could not find that file in the installation directory. However, if I set it manually, then the setup.py file runs fine.
Uwe Korn / @xhochy:
The conda_build_config.yaml
only works when you build with conda build
but in this case, we aren't using it but calling cmake / the compiler directly, thus you need to export CONDA_BUILD_SYSROOT=<sdk-location>
.
Ian Mateus Vieira Manor: Having the same problem running
cmake install
on OSX, but have no
/build/jemalloc_ep-prefix/src/jemalloc_ep/dist
directory to delete.
Ian Mateus Vieira Manor: Solved the jemalloc problem on my machine by installing macOS SDK headers.
cd /Library/Developer/CommandLineTools/Packages/
open macOS_SDK_headers_for_macOS_10.14.pkg
Todd Farmer / @toddfarmer: Transitioning issue from Resolved to Closed to based on resolution field value.
My attempts to build pyarrow from source are failing. I've set up the conda environment using the instructions provided in the Develop instructions, and have tried this on both Debian and OSX. When I run CMAKE in debug mode on OSX, the output is:
After I run make -j4, the output is:
And the output of the jemalloc log file is:
Any help / guidance I can get is appreciated.
Environment: OSX, Debian, Python==3.6.7 Reporter: Gregory Hayes
Externally tracked issue: https://github.com/apache/arrow/issues/3948
Note: This issue was originally created as ARROW-4935. Please see the migration documentation for further details.