CODEWITHSUNDEEP
pythontensorflowbuildpipbazel
Shagas
Shagas

Reputation: 605

Tensorflow bazel build doesn't generate .whl file

I'm trying to build tensorflow from sources. I have done so successfully once using the guide on my laptop and now I'm trying on my desktop. The .whl file fails to show up in the /tmp directory, which leads to a failure to install the pip package in the next step. I cannot find the .whl file anywhere. I've tried reinstalling bazel and re-downloading the tensorflow git repo and doing the whole procedure from scratch many times over and it simply fails to show up in /tmp. I don't feel comfortable enough to modify the python package build script to try a different directory. Can anyone give some advice as to what I can try? (tensorflow installs from pip successfully the usual way).

Invoking the build command after a successful build gives me the following output:

WARNING: /home/shagas/Data/SW/tensorflow/tensorflow/contrib/learn/BUILD:15:1: in py_library rule //tensorflow/contrib/learn:learn: target '//tensorflow/contrib/learn:learn' depends on deprecated target '//tensorflow/contrib/session_bundle:gc': No longer supported. Switch to SavedModel immediately.
INFO: Analysed target //tensorflow/tools/pip_package:build_pip_package (0 packages loaded).
INFO: Found 1 target...
Target //tensorflow/tools/pip_package:build_pip_package up-to-date:
  bazel-bin/tensorflow/tools/pip_package/build_pip_package
INFO: Elapsed time: 0.243s, Critical Path: 0.00s
INFO: Build completed successfully, 1 total action

But I can't find the .whl anywhere

Upvotes: 3

Views: 2409

Answers (2)

Shagas
Shagas

Reputation: 605

It seems that I have been missing a step which makes the .whl package out of the build which I thought was intended for another case.

bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

Upvotes: 13

László
László

Reputation: 4281

If the build succeeds, then Bazel must have built something.

Bazel usually prints the paths of some of the top-level output files at the end of a successful build. The --show_outputs=<number> flag sets the limit for the number of paths Bazel prints. If you don't see the built PIP package's path here, you can also look for it under bazel-bin/path/to/package/* or bazel-genfiles/path/to/package/*.

Upvotes: 0

Related Questions