Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
macOS 10.13.6 with clang 6.0.1.
-
Mesosphere Sprint 2018-25
-
2
Description
Seems like this was introduces with commit a211b4cadf289168464fc50987255d883c226e89. Linking libprocess-tests on macOS with enabled gRPC fails with
Undefined symbols for architecture x86_64: "grpc::TimePoint<std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > > >::you_need_a_specialization_of_TimePoint()", referenced from: process::Future<Try<tests::Pong, process::grpc::StatusError> > process::grpc::client::Runtime::call<std::__1::unique_ptr<grpc::ClientAsyncResponseReader<tests::Pong>, std::__1::default_delete<grpc::ClientAsyncResponseReader<tests::Pong> > > (tests::PingPong::Stub::*)(grpc::ClientContext*, tests::Ping const&, grpc::CompletionQueue*), tests::Ping, tests::Pong, 0>(process::grpc::client::Connection const&, std::__1::unique_ptr<grpc::ClientAsyncResponseReader<tests::Pong>, std::__1::default_delete<grpc::ClientAsyncResponseReader<tests::Pong> > > (tests::PingPong::Stub::*&&)(grpc::ClientContext*, tests::Ping const&, grpc::CompletionQueue*), tests::Ping&&, process::grpc::client::CallOptions const&)::'lambda'(tests::Ping const&, bool, grpc::CompletionQueue*)::operator()(tests::Ping const&, bool, grpc::CompletionQueue*) const in libprocess_tests-grpc_tests.o ld: symbol(s) not found for architecture x86_64 clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation)