-
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
Virtual TF package breaks tf.sysconfig based include path #29532
Comments
byronyi
pushed a commit
to bytedance/tensorflow
that referenced
this issue
Jun 7, 2019
As tensorflow is a virtual Python package now, the corresponding path should be under tensorflow_core. This fixes tensorflow#29532. Signed-off-by: Bairen Yi <yibairen.byron@bytedance.com>
byronyi
pushed a commit
to bytedance/tensorflow
that referenced
this issue
Jun 7, 2019
As tensorflow is a virtual Python package now, the corresponding path should be under tensorflow_core. This fixes tensorflow#29532. Signed-off-by: Bairen Yi <yibairen.byron@bytedance.com>
Sorry about that, will fix today. |
I think this should be fixed now, but let me know if not and I missed something. |
sleighsoft
pushed a commit
to sleighsoft/tensorflow
that referenced
this issue
Jun 12, 2019
When making the virtual pip changes, by moving code to new directory, required headers and shared object are no longer vizible where they should. This should fix that. PiperOrigin-RevId: 252100366
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As f1ffa02 landed yesterday, the framework library is now moved from
tensorflow
totensorflow_core
and the include path also changed totensorflow_core/include
.tf.sysconfig.get_include
andtf.sysconfig.get_lib
should be changed accordingly but they are not. This breaks downstream packages such as horovod and tensorflow_io that build custom ops and link to TF. It also means any binary distributions of these packages will break binary backward compatibility with this change.See horovod/horovod#1129 for a reproducing procedure.
Ping @mihaimaruseac @yifeif
The text was updated successfully, but these errors were encountered: