Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build failure on macOS #19762

Closed
josefsachsconning opened this issue Dec 29, 2016 · 8 comments · Fixed by #18910
Closed

build failure on macOS #19762

josefsachsconning opened this issue Dec 29, 2016 · 8 comments · Fixed by #18910
Labels
system:mac Affects only macOS

Comments

@josefsachsconning
Copy link
Contributor

fresh clone of master branch at 19f81ac

[ 75%] Building CXX object lib/ExecutionEngine/Orc/CMakeFiles/LLVMOrcJIT.dir/OrcMCJITReplacement.cpp.o
[ 75%] Building CXX object lib/ExecutionEngine/Orc/CMakeFiles/LLVMOrcJIT.dir/OrcRemoteTargetRPCAPI.cpp.o
In file included from /Users/sachs/src/julia-master/deps/srccache/llvm-3.9.1/lib/ExecutionEngine/Orc/OrcRemoteTargetRPCAPI.cpp:10:
In file included from /Users/sachs/src/julia-master/deps/srccache/llvm-3.9.1/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetRPCAPI.h:21:
In file included from /Users/sachs/src/julia-master/deps/srccache/llvm-3.9.1/include/llvm/ExecutionEngine/Orc/RPCUtils.h:35:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1447:23: error:
      'future_error' is unavailable: introduced in macOS 10.8
                      future_error(make_error_code(future_errc::broken_promise))
                      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note:
      'future_error' has been explicitly marked unavailable here
class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
                                                              ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1621:23: error:
      'future_error' is unavailable: introduced in macOS 10.8
                      future_error(make_error_code(future_errc::broken_promise))
                      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note:
      'future_error' has been explicitly marked unavailable here
class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
                                                              ^
2 errors generated.
make[4]: *** [lib/ExecutionEngine/Orc/CMakeFiles/LLVMOrcJIT.dir/OrcRemoteTargetRPCAPI.cpp.o] Error 1
make[3]: *** [lib/ExecutionEngine/Orc/CMakeFiles/LLVMOrcJIT.dir/all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [scratch/llvm-3.9.1/build_Release/build-compiled] Error 2
make: *** [julia-deps] Error 2
@josefsachsconning
Copy link
Contributor Author

My previous successful build was at 229d096

@dpsanders
Copy link
Contributor

FWIW, I'm seeing the same.

@andreasnoack
Copy link
Member

Try to merge #18910 and distclean-llvm

@josefsachsconning
Copy link
Contributor Author

When I apply the changes in #18910, the build succeeds.

@dpsanders
Copy link
Contributor

👍

@tkelman tkelman added the system:mac Affects only macOS label Dec 30, 2016
@stevengj
Copy link
Member

I'm on macOS 10.12.2, and initially got the future_error above, then pulled the latest master and did make -C deps distclean-llvm && make, and now I'm getting

Scanning dependencies of target clang_rt.eprintf
[ 38%] Building C object projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.eprintf.dir/eprintf.c.o
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)
make[4]: *** [projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.eprintf.dir/eprintf.c.o] Error 1
make[3]: *** [projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.eprintf.dir/all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [scratch/llvm-3.9.1/build_Release/build-compiled] Error 2

@andreasnoack
Copy link
Member

Might be #18920

@stevengj
Copy link
Member

Ah, thanks.

(One thing that might be helpful is to include the error message that a PR solves in the PR, so that searching for e.g. "invalid deployment target" will turn up the PR.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
system:mac Affects only macOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants