-
Notifications
You must be signed in to change notification settings - Fork 74k
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
tensorflow/core/framework/op_def.pb.h:10:40: fatal error: google/protobuf/port_def.inc: No such file or directory #27697
Comments
Un-assigning so this'll get into our GitHub triaging system (pinging @rthadur for this). |
Also: @meteorcloudy |
@seanpmorgan @gunan Is tf addons somehow using this BUILD file? tensorflow/third_party/systemlibs/protobuf.BUILD Lines 15 to 25 in 3fb94ab
@acozzette Dose it make sense to you to add google/protobuf/port_def.inc here?
|
We don't use the BUILD file itself. We link to the pre-compiled It looks like the op_def.pb header file is referencinng a file which is not where it is expected after the new protobuf install.
|
Same here, we're not using Bazel. |
Looks like the problem is when creating the pip package, we missed to copy header files that has tensorflow/tensorflow/tools/pip_package/build_pip_package.sh Lines 128 to 130 in 1cdae49
I'll send a fix for this. |
Still seeing this issue in the 20190412 nightly. Was this merged in for that nightly? If so I'm not sure the correct fix is in place.
|
+1, it's still broken in the current tf-nightly. |
Turned out we also need to fix
|
I verified on my local machine, fixing this file works. Sending a fix from internal. |
Can anyone verify |
It worked on my Mac, Ubuntu 18.04 and your |
@alsrgv Thanks! Hopefully this time it will work |
Removing -type flag because it is unnecessary and on some platform it doesn't accepted multiple types, which caused: find: Arguments to -type should contain only one letter Fourth try to fix tensorflow#27697#issuecomment-486956391 PiperOrigin-RevId: 245433173
@meteorcloudy, I can confirm that both Mac and Linux nightly builds are operational. Could you pick this fix to the 1.4 branch? |
@bananabowl can you cherry-pick this fix? |
Sure - this is part of #28296 |
Hi,
I am using the headers generated by //tensorflow:install_headers . |
Sorry to hear that Andrey :(
@mihaimaruseac - I noticed you made some changes since the original fix,
was this
<fd5d844#diff-aa53f753fc372beaeb504d505c278203>
or
a subsequent change meant to fix this issue?
…On Mon, Jun 24, 2019 at 7:00 AM Andrey Hristov ***@***.***> wrote:
Hi,
I experience this problem with 1.14.0 . From what I see in the sources, as
well as bananabowl's comment / reference to the cherry picks, the needed
changes are in 1.14.0. Still getting the problem.
Here is the error:
In file included from ./deps/tensorflow-headers-1.14.0/tensorflow/core/framework/tensor_shape.h:22:0,
from ./deps/tensorflow-headers-1.14.0/tensorflow/core/framework/tensor.h:23,
from ./deps/tensorflow-headers-1.14.0/tensorflow/cc/framework/ops.h:21,
from ./deps/tensorflow-headers-1.14.0/tensorflow/cc/client/client_session.h:24,
from ./include/detect_tensorflow.hpp:5,
from src/detect_tensorflow.cpp:1:
./deps/tensorflow-headers-1.14.0/tensorflow/core/framework/types.pb.h:10:10: fatal error: google/protobuf/port_def.inc: No such file or directory
#include <google/protobuf/port_def.inc>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am using the headers generated by //tensorflow:install_headers .
Platform : AARCH64
OS : Ubuntu 18.04 LTS
Hardware: Nvidia Xavier AGX
Software: TensorFlow 1.14.0 from a source release. Compiled with Bazel
0.24.1 (from a dist package).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27697?email_source=notifications&email_token=AKEVL2DVBJ3KOFTZLYRTIZDP4DHRTA5CNFSM4HEW4MV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYM7ZXQ#issuecomment-505019614>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEVL2HIORNS6JG5AEYT4CTP4DHRTANCNFSM4HEW4MVQ>
.
|
Hi, the fd5d844 change is for virtual pip, should be on master only, not on a release branch. There's also some changes related with moving protobuf definitions around, but again, that should only be on master. |
I tried the master branch. Interestingly it seems to be 1.13.1 (because the generated PIP file is tensorflow-1.13.1-cp36-cp36m-linux_aarch64.whl). The problem persist but it could be that master is not the right branch (is not actively used). Is it? |
@andreyhristov The master branch is the develop branch.
|
And in 1.14 branch, the ".inc" file headers also exist but under
|
ok guys, right, I found the file. The problem was that I needed to add the path to protobuf_archive to the include path of the compiler. I compiles now and it works! (I had asserts with 1.12.0 on batch inference which are gone). Last question, why does master seem to be with version 1.13.1 ? Do you guys change the version after branching for release? |
Yes, it's embedded here:
@gunan Is this intentionally? |
Fixed the version number in 4a017ec |
Hi, |
Hello, I'm still seeing this issue with tf1.14.0 while compiling a custom op kernel. I'm on windows, installed TF using pip. Is there a way to fix this issue without building the sources manually (by using bazel)? Any help is appreciated. Thanks! |
try include the dir solve this issue? like: |
Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information
You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
As of
1.14.1-dev20190409
, custom plugins fail to build with the following error:This seems to be related to 6168f47. It appears that not all the files are placed in the proper locations after the installation.
Describe the expected behavior
Plugins should build successfully.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
cc @martinwicke @gunan
The text was updated successfully, but these errors were encountered: