Tensorflow failed to compile #18450
Assignees
Comments
|
try gcc 4~6 don't use gcc7 |
|
I'm also facing build problems even with gcc-6. System information Logs: |
|
gcc is not the problem(tried 4-6). It has worked with gcc 7.3.1 before as well. The only changes to programs related to tensorflow is the tensorflow commit itself and bazel. |
|
To corroborate, I just experienced the same problem/error as in the original post. I'd compiled tf 1.7 successfully previously (Ubuntu 14.04.4) but just did an OS upgrade (Ubuntu 14.04.5) and now I get the same error. Several packages were updated---I'm not sure what may have been the cause. |
|
Getting back to Moocow9m's issue. I just had the same problem. It was the bazel update from a couple of days ago. Try un-installing version 12 and get the 11.1 bazel deb file and install form that. I also had to add --action_env PATH="$PATH" to keep it from forgetting where Python was (I'm using Anaconda3) I also have the following cuda.conf in ld.so.conf.d |
|
@dbkinghorn It does compile with the older bazel build, however since version 0.12.0 can compile branch r1.8 I still think this might be a tensorflow issue in the r1.7 branch. |
|
I also can compile tf master with bazel 0.12. However, I'm still befuddled that the same tf commit (from branch 1.7) failed to compile after a suite of package updates. That doesn't necessarily mean it wasn't a tf issue in 1.7, just that it wasn't manifest until after a separate update (which I don't think changed bazel). |
|
Maybe this problem is caused by bazel. I could compile branch r1.6 with bazel 0.11.1. If I update bazel from 0.11.1 to 0.12.0, it will be failed. |
|
I just pulled the latest commits, and it builds fine. |
|
@rharish101 what version of bazel did you use? What is your OS? |
|
@LuBingtan , Yeah, must be the problem of bazel 0.12. I updated bazel from 0.12 to 0.11 and it seems fine now. |
|
Had similar issue building TF 1.7 with Bazel 0.12. Downgrading bazel to 0.11 seems to fix the issue |
|
Downgrading to Bazel 0.11.1 may fix this issue currently |
|
I confirm that downgrading bazel from 0.12.0 to 0.11.1 fixes the exact error. To downgrade, the only way I found is $ sudo apt-get install -y --no-install-recommends bash-completion g++ zlib1g-dev
$ curl -LO "https://github.com/bazelbuild/bazel/releases/download/0.11.1/bazel_0.11.1-linux-x86_64.deb"
$ sudo dpkg -i bazel_*.debCopied and modified from this bazel thread. |
|
@Moocow9m Here are my specs: |
|
this fix by @zhanwenchen helped me |
ghost
mentioned this issue
|
It's the problem caused by bazel, version 0.11 is fine with me. |
|
A better fix whould be to cherry-pick 15bda92. |
|
I had exactly the same issue, as soon as I switch from Bazel 0.12 to Bazel 0.11 the compilation went smoothly. |
|
I think this issue can be closed since #17508 has been merged to all branches and v1.7.1 contains the fix. |
|
--config=cuda_clang mabe close this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem
While compiling tensorflow build failed. I just pulled the latest commit(92e6c3e) from the r1.7 branch. I also updated bazel (from 0.11.1 to 0.12.0) and some other programs(should be irrelevant to tensorflow) beforehand.
Source code / logs
`ERROR: /home/UserHome/.cache/bazel/_bazel_UserHome/ab33c8274551e1ea3125872a4c4e7db9/external/jpeg/BUILD:126:12: Illegal ambiguous match on configurable attribute "deps" in @jpeg//:jpeg:
@jpeg//:k8
@jpeg//:armeabi-v7a
Multiple matches are not allowed unless one is unambiguously more specialized.
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:
/home/UserHome/.cache/bazel/_bazel_UserHome/ab33c8274551e1ea3125872a4c4e7db9/external/jpeg/BUILD:126:12: Illegal ambiguous match on configurable attribute "deps" in @jpeg//:jpeg:
@jpeg//:k8
@jpeg//:armeabi-v7a
Multiple matches are not allowed unless one is unambiguously more specialized.
INFO: Elapsed time: 1.086s
FAILED: Build did NOT complete successfully (3 packages loaded)`
UPDATE: The r1.8 branch compiles successfully. The 1.8 branch might have a fix? Or perhaps a dependency was updated and that fixed it?
The text was updated successfully, but these errors were encountered: