Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 692342 - sci-libs/tensorflow-1.14.0-r1 with net-libs/grpc-1.23.0 - ./tensorflow/core/distributed_runtime/rpc/grpc_call.h:143:7: error: 'grpc::ServerAsyncResponseWriter' has not been declared
Summary: sci-libs/tensorflow-1.14.0-r1 with net-libs/grpc-1.23.0 - ./tensorflow/core/d...
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Jason Zaman
URL:
Whiteboard:
Keywords:
: 692892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-17 10:25 UTC by Helmut Jarausch
Modified: 2019-12-09 04:34 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build log xz-compressed (tensorflow-1.14.0-r1.build.xz,30.68 KB, application/octet-stream)
2019-08-17 16:37 UTC, Helmut Jarausch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Jarausch 2019-08-17 10:25:22 UTC
With the recent net-libs/grpc-1.23.0 (and net-libs/google-cloud-cpp recompiled with this installed)
sci-libs/tensorflow-1.14.0-r1  fails to compile

In file included from tensorflow/core/distributed_runtime/rpc/grpc_master_service.cc:37:
./tensorflow/core/distributed_runtime/rpc/grpc_call.h:143:7: error: 'grpc::ServerAsyncResponseWriter' has not been declared

Downgrading to net-libs/grpc-1.22.1 fixes the problem.
Comment 1 Jonas Stein gentoo-dev 2019-08-17 11:47:49 UTC
please add the logs, so that we see what is going on.
https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket
...and reopen then.
Comment 2 Helmut Jarausch 2019-08-17 16:37:16 UTC
Created attachment 587216 [details]
build log  xz-compressed
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2019-08-27 06:23:56 UTC
*** Bug 692892 has been marked as a duplicate of this bug. ***
Comment 4 Jason Zaman gentoo-dev 2019-12-09 04:34:01 UTC
I've dropped tf-1.14 from the tree, please file a new bug/reopen if this still happens :)