-
Notifications
You must be signed in to change notification settings - Fork 74.4k
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
Add link libtensorflow_framework.so => libtensorflow_framework.so.1 #30175
Comments
Unfortunately a wheel file is just a fancy zip archive so a symbolic link gets translated into a new copy of the file. So the file gets included twice, bloating the size of the pip package. We will slowly evolve into a state where we can have the symlink in place, but it will take some time, unfortunately. |
The recommended approach for extending TF is to use tf.sysconfig.get_link_flags() instead of relying on manually specifying shared object path. |
Thanks for the quick reply. In the mean time, do you have any solution for a distutils-based package that has the following:
Because of the .1 suffix, the linker is not finding libtensorflow_framework. Putting the full name (libtensorflow_framework.so.1) doesn't work either. I had to either revert to Tensorflow 1.13.2 or add the symlink manually. |
Inspired by @byronyi 's comment, I tried what |
@mdorier Can you please let us know if you are happy to close if no issue persists |
hello mdorier , can you show the code which help you solved this issue, i met the same problem |
@mathlf2015 Right now I still sort of hard-code |
mdorier ,thank you . when i try to load a xx.so by load_library.py, i will always get the error ,i don't know how to us the "tf.sysconfig.get_link_flags()" to solve this . could you give me some advices. |
Not sure what you've done so far but on my laptop on Debian with tensorflow 2.1.0 installed via Then if when trying to load the library you get a |
|
System information
Describe the feature and the current behavior/state.
Starting from TensorFlow 1.14.0, the pip packages come with a libtensorflow_framework.so.1 instead of a libtensorflow_framework.so. This breaks the build process of codes that extend tensorflow. Adding a symbolic link libtensorflow_framework.so => libtensorflow_framework.so.1 would greatly help.
The text was updated successfully, but these errors were encountered: