current ebuild specifies bazel-0.24* bazel-0.26* bazel-0.27*
As of 12-07-2019: # emerge -av tensorflow These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-util/bazel-0.27.2::gentoo USE="-examples -tools" 0 KiB [ebuild N ] sci-libs/tensorflow-2.1.0_rc0::gentoo USE="python -cuda -mpi -xla" CPU_FLAGS_X86="sse sse2 -avx -avx2 -fma3 -fma4 -sse3 -sse4_1 -sse4_2" PYTHON_TARGETS="python3_6 -python3_5 -python3_7" 0 KiB [ebuild N ] sci-libs/tensorflow-estimator-2.0.0::gentoo PYTHON_TARGETS="python3_6 -python3_5 -python3_7" 0 KiB Total: 3 packages (3 new), Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-util/bazel:0 (dev-util/bazel-1.2.0:0/0::gentoo, ebuild scheduled for merge) conflicts with =dev-util/bazel-0.27* required by (sci-libs/tensorflow-2.1.0_rc0:0/0::gentoo, ebuild scheduled for merge) ^ ^^^^^
I see tensorflow for stable AMD64 pulling stable version of Bazel (which is still wrong): # equery g tensorflow ... `-- dev-util/bazel-0.24.1 (=dev-util/bazel-0.24*) amd64 Unmasking ~amd64 then works as expected: # equery g tensorflow ... -- dev-util/bazel-0.27.2 (=dev-util/bazel-0.27*) ~amd64 -- dev-util/bazel-1.2.0 (>=dev-util/bazel-0.20) ~amd64
Sorry, unmasking ~amd64 is still set to older version: (>=dev-util/bazel-0.20) If Tensorflow 2 needs >=dev-util/bazel-0.27.1 then this is still a bug.
Tensorflow-2.1.0_rc0 says it needs bazel-0,27.1 or greater if you try to build with bazel-0.24.1 Tensorflow 2.0.0 will build with bazel-0.24 bazel-0.26 or bazel-0.27 Tensorflow 2.1.0_rc0 does not build with bazel-1.2.0. I did manage to build with bazel-0.27.2 but I had to downgrade jsoncpp to 1.9.1 jsoncpp-1.9.2-r1 caused build failures with headers not found. I don't know if tensorflow-2.1.0_rc0 will build with bazel-0.29 or bazel-1.1.0 This should be tested. Right now the tensorflow-2.1.0_rc0 has the same bazel build dependencies at tensorflow-2.0,0 which are incorrect. Both tensorflows need <=dev-libs/jsoncpp-1.9.1 to build.
*** Bug 702224 has been marked as a duplicate of this bug. ***
only bazel-0.27 and bazel-0.29, but yeah the dep was wrong, thanks :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a3dc69074dcad86d4c95e024d231c90c62483152 commit a3dc69074dcad86d4c95e024d231c90c62483152 Author: Jason Zaman <perfinion@gentoo.org> AuthorDate: 2019-12-08 11:18:22 +0000 Commit: Jason Zaman <perfinion@gentoo.org> CommitDate: 2019-12-08 17:25:26 +0000 sci-libs/tensorflow: fix bazel, jsoncpp deps Also add a message about setting cuda compute capability Closes: https://bugs.gentoo.org/695428 Closes: https://bugs.gentoo.org/697864 Closes: https://bugs.gentoo.org/702222 Package-Manager: Portage-2.3.79, Repoman-2.3.16 Signed-off-by: Jason Zaman <perfinion@gentoo.org> sci-libs/tensorflow/Manifest | 1 + sci-libs/tensorflow/tensorflow-1.15.0_rc0.ebuild | 16 ++++++++++++++-- sci-libs/tensorflow/tensorflow-2.0.0.ebuild | 16 ++++++++++++++-- sci-libs/tensorflow/tensorflow-2.1.0_rc0.ebuild | 19 ++++++++++++++++--- 4 files changed, 45 insertions(+), 7 deletions(-)
