-
Notifications
You must be signed in to change notification settings - Fork 1.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
No such file:dmlab.lds Error! #106
Comments
Can you provide the Bazel invocation that caused this error? |
$ cd lab When I ran the last bold line, finally, the error took place:( |
I have same issue with Dockerfile from scalable_agent project
|
I solved the issue while working with gh://deepmind/scalable_agent project. It's because of bazel 0.17.1 that was released 5 days ago. (2018-09-14) The problem is that the following dockerfile code line,
gets the latest stable version which is bazel 0.17.1. for the deepmind/scalable_agent issue #16
to
And It should build without errors. (as of 2018-09-18) You can use the Dockerfile here |
Unlucky, https://github.com/bazelbuild/bazel/releases/download/$BAZEL_VERSION/bazel-$BAZEL_VERSION-installer-linux-x86_64.sh is not available now:( |
It's meant to be used inside dockerfile (that's why Try with this then :) |
Thanks a lot for reporting this! There has been a change in Bazel semantics. It was actually fixed internally a while ago, but I missed that and forgot to release that change. Fixed in 8ca0776. |
When I run the installation of deepmind lab on Ubuntu16.04, all dependencies have been installed, but there still some errors:
ERROR: /home/tommy/IMPALA/lab/BUILD:895:1: Linking of rule '//:libdmlab_headless_hw.so' failed (Exit 1)
gcc: error: :dmlab.lds: No such file or directory
Target //python/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 125.820s, Critical Path: 72.23s
INFO: 835 processes: 835 linux-sandbox.
FAILED: Build did NOT complete successfully
How to fix it, please?
The text was updated successfully, but these errors were encountered: