Created attachment 541104 [details, diff] Fixes the NoneType error which can cause the ebuild to fail. This bug was actually fixed in TensorFlow 1.9.0-rc2. I was a bit surprised to see this ebuild bumped down back to a pre-rc2 source tree. However, let's get to the point: Building this version of TensorFlow can fail with the error described in this bug report upstream: https://github.com/tensorflow/tensorflow/issues/20233 I quote: "/var/tmp/portage/sci-libs/tensorflow-1.9.0_rc1/work/bazel-base-python3_6/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/tools/api/generator/create_python_api.runfiles/org_tensorflow/tensorflow/tools/api/generator/create_python_api.py", line 182, in get_api_init_text package not in module.__name__): TypeError: argument of type 'NoneType' is not iterable Target //tensorflow/tools/pip_package:build_pip_package failed to build INFO: Elapsed time: 3202.457s, Critical Path: 83.98s INFO: 4901 processes, local. FAILED: Build did NOT complete successfully FAILED: Build did NOT complete successfully Which is essentially the error I got when trying to compile the 1.9.0 ebuild. This can be fixed by applying the patch I've attached, which is the commit taken from the TensorFlow master which fixes this bug. I added this commit to my user patches and the error went away.
I have this error too.
This should be fixed in tensorflow-1.10.0
