Failed building wheel for mujoco-py #66
Comments
|
I've got similar problems. When I execute
The system is Ubuntu 16.04 LST with Python 3.5.2, and the ~/.mujoco directory is prepared with a valid mjkey.txt. Also, the mujoco150/bin/simulate works well.
I think these might be the same problem, have you solved it? |
|
Looks like there might be a problem where If you uninstall it and add Edit: nevermind, it looks like both have the correct latest version pulled, so not a cache issue. |
|
@pat-coady can you verify that your activation key isn't expired and the file matches the one in mjpro150/bin (or whatever key ./simulate was using)? Possibly a key for a different version of mujoco? That's different than the error message when the key file can't be found, so my thought is it found the file but for some reason the key failed to validate (possibly for a different OS/machine, out of date/expired, for a different version of mujoco, or possibly for other reasons). |
|
@cxy1997 I think your issue is a different thing -- would you mind filing a separate issue for that? |
|
@machinaut - The diff on the mjkey.txt files came up clean. The key is only a few days old and was issued for the machine I'm running on. I ended up installing mujoco-py ver0.5.7 (and mjpro131) as a workaround, and that is working fine. Regardin @cxy1997 post - could be slightly related to problem I'm seeing. My install also froze exactly like they described. I gave it 10 minutes. But the spinning bar was frozen. When I pressed ENTER I got the rest of the log file that I cut and pasted above. Thanks for looking into this. |
|
@machinaut and @pat-coady - In fact I encountered another problem, and when dealing with it I figured out an alternative way to install mujoco-py. Here's the story. After I tried to install it with I found that some of the dependencies in |
|
@cxy1997 - I also lost my keyboard and mouse by blindly installing all the dependencies listed in docker file (my fault, not mujoco-py problem). Fortunately I was able to fix that without a complete OS reinstall. I tried your procedure and it seems like some progress. But I still can't get a working installation. I get to the point where it is "Cythonizing" things the first time I import mujoco-py. But then I go around and around with permission denied problems, then rerunning with sudo, then gcc errors. I started to flail again and gave up. Fortunately as able to revert to 0.5.7 again and am running for now. |
|
@pat-coady - The 'Cythonizing' thing you mentioned is common when
Ather that, you should be able to |
|
@cxy1997 - Yes, I had gotten past the Cythonize (although I had to run 'sudo python' - otherwise permission problems). Then I ran into another hurdle (it is all a blur now). Then I finally went to train my agent and got a 'mujoco-py' not installed sort of error. Along with all of this, my jupyter notebook installation stopped working. Reinstalling Ubuntu now as too many things seem messed up at this point. I'm going to wait and see if the straightforward pip approach gets repaired. And stick with 0.5.7 version for now. |
|
Ok, here is a new log file. Slightly different error now: sudo -H pip3 install -U 'mujoco-py<1.50.2,>=1.50.1' Failed building wheel for mujoco-py Rolling back uninstall of mujoco-py |
|
In that last one, the compiler failed with It's looking for that file with the include flag |
|
Ok, seems we are getting close. No, my header files are in ~/.mujoco/mj150/include: pco@pco-ThinkPad-T540p:~/.mujoco/mjpro150/include$ ls Seems odd they would be expected in /root/.mujoco? |
|
@machinaut - I put a copy of the .mujoco directory in /root. It got past that error, but then complained about glfw3. I installed libglfw3 libglfw3-dev. And then I ended up right back where I started with the error log I first posted. |
|
@pat-coady same as first error means it's back to Can you confirm you're able to run the mujoco 1.50 samples using the key provided (e.g. |
|
@machinaut - yes, back to original error with strange binary characters and the Invalid activation key. This opens blue window with 'Drag-and-drop model file here.' I wonder why I am able to install and run mujoco-py 0.5.7 with no problems (albeit with mjpro131)? I didn't have to install any dependencies are anything else, "it just worked". Thanks a lot, Pat |
|
I've still not been able to replicate the error with the strange binary characters. Do you have any non-ASCII characters in any paths? That's not something we've tested much. |
|
@machinaut - I've got a very boring filesystem. Just exactly what you get from a fresh Ubuntu install except with 2 other directories off my user home: Projects and Programs (which only contains pycharm). Maybe most exotic character in my file names is an '_'. Even my .bashrc is untouched from Ubuntu install except for adding mujoco to LD_LIBRARY_PATH (I've tried pointed this to 131 and 150, but doesn't make a difference). Also, not much installed, usual machine learning stuff: scipy, sklearn, numpy, matplotlib, seaborn, tensorflow, google chrome, sublime, pycharm, pandas. Nothing fancy. Very odd. I'll probably be creating building a fresh setup on AWS in a couple and will likely put mujoco-py on that. I'll document every step I do in case that fails. |
|
Had the exact same issue with @pat-coady and just ended up with installing mjpro131 with mujoco-py==0.5.7 I also have pretty boring filesystem. taegyunk@taegyunk-xubuntu$> pip3 install -U 'mujoco-py<1.50.2,>=1.50.1' error Press Enter to exit ... Failed building wheel for mujoco-py Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/taegyunk/pip-build-9jt58lck/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/taegyunk/pip-79b6a9px-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/taegyunk/pip-build-9jt58lck/mujoco-py/ |
|
I'm also running this install and it's failing. My install is in /home/myusername/.mujoco/mjpro150 and I'm running Ubuntu 16.04. ➜ ~ pip3 install mujoco-py --no-cache Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-wf46s7j1/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-7bmql548-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-wf46s7j1/mujoco-py/ |
|
Any advances on this? I'm having the same error on ubuntu 14.04 using a conda environment. I tried to run setup() build --verbose, but the output is the same: |
|
I'm also having the same error on ubuntu 16.10 using a conda env. |
|
It's same problem on my ubuntu 16.04.3 LTS using virtualenv. ... |
|
I have same problem too, on Ubuntu 17.04 error error Press Enter to exit ... Failed building wheel for mujoco-py Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-npqsffv_/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-qi6j4_9l-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-npqsffv_/mujoco-py/ sh: 2: [ Press Enter to exit ... Failed building wheel for mujoco-py Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-npqsffv_/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-qi6j4_9l-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-npqsffv_/mujoco-py/ |
|
Same error with: "ERROR: Invalid activation key" |
|
I can also confirm this behavior on Ubuntu 16.04. Any other ideas of how we can help troubleshoot this, @machinaut ? |
|
Try cloning the repo instead: |
|
I also have the same issue, and it is so annoying. When read the email send from mujoco.pro again, I found some inconsistency between their suggestion and the installation suggestion in openAI.mujoco-py see below: I tried as this but the error is then: made me mad...........wtf.... |
|
thanks for mentioning. I also copied the key into ~/.mujoco and
~/.mujoco/mjpro150/bin. Still, doesn't work for me.
#Failed building wheels//
thank you for sharing...
…On 10 September 2017 at 20:30, rhiga2 ***@***.***> wrote:
@fishchian <https://github.com/fishchian> I had similar issues. I ended
up copying mjkey.txt into ~/.mujoco and ~/.mujoco/mjpro150/bin. Not sure
why that worked for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdD5PjSOlncRwRzdmNHXvq90vxWqTYeCks5shKlngaJpZM4OXK7h>
.
--
Kunxun (Fish) Qian
Salk Institute
Research intern
Terry Sejnowski's lab (CNL)
|
|
Just to heads up, luckily Mujoco 0.5.7 works well for me. it is compatible with Python2 and python3, hope this information helps |
|
Are there any updates on the progress with current issues? Installation of 0.5.7 works well and out of box as it should be, but looks like it's impossible to install and make 1.5.x working on quit standard configuration - Ubuntu 16.04. I suppose all these issues can be considered to be solved only when just "pip install mujoco-py" or "pip install -e ." work. |
|
@fishchian how do you know the commands for the older version? The documentation seems to be for 1.5 |
|
@sritee Both would probably work https://github.com/openai/mujoco-py |
|
I also encountered similar problem but was able to solve it by switching to mjpro131. You should first download mjpro131 from the official site and then move it to |
|
Are there any updates on this issue? I am getting this issue after confirming that I can run mujoco in the same folder/terminal where I am attempting to install And the following results from various install commands, |
|
@cathywu I think you may try mjpro131 instead of mjpro150... |
|
git clone the mujoco-py to where you wish to. |
|
I'm trying to build a docker image of universe. I'm running the following command:
I have mujoco installed at ~/.mujoco/mujoco200. I have the license key at ~/.mujoco/. I'm getting the following error: Traceback (most recent call last): Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-da8i39jm/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-vl7solc7/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-da8i39jm/mujoco-py/ |
Any luck with this! I am stuck |
and others
Here is the full log:
`pip3 install -U 'mujoco-py<1.50.2,>=1.50.1'
Collecting mujoco-py<1.50.2,>=1.50.1
Using cached mujoco-py-1.50.1.7.tar.gz
Requirement already up-to-date: glfw>=1.4.0 in /usr/local/lib/python3.5/dist-packages (from mujoco-py<1.50.2,>=1.50.1)
Requirement already up-to-date: numpy>=1.11 in ./.local/lib/python3.5/site-packages (from mujoco-py<1.50.2,>=1.50.1)
Requirement already up-to-date: Cython>=0.25.2 in /usr/local/lib/python3.5/dist-packages (from mujoco-py<1.50.2,>=1.50.1)
Requirement already up-to-date: imageio>=2.1.2 in ./.local/lib/python3.5/site-packages (from mujoco-py<1.50.2,>=1.50.1)
Requirement already up-to-date: pillow in ./.local/lib/python3.5/site-packages (from imageio>=2.1.2->mujoco-py<1.50.2,>=1.50.1)
Requirement already up-to-date: olefile in ./.local/lib/python3.5/site-packages (from pillow->imageio>=2.1.2->mujoco-py<1.50.2,>=1.50.1)
Building wheels for collected packages: mujoco-py
Running setup.py bdist_wheel for mujoco-py ... -
error
Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-lfrvbntl/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/tmpfe_jl9xipip-wheel- --python-tag cp35:
running bdist_wheel
running build
Compiling /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/cymj.pyx because it changed.
[1/1] Cythonizing /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/cymj.pyx
running build_ext
building 'mujoco_py.cymj' extension
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/gl
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py -I/home/pco/.mujoco/mjpro150/include -I/home/pco/.local/lib/python3.5/site-packages/numpy/core/include -I/usr/include/python3.5m -c /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/cymj.c -o /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/cymj.o -fopenmp -w
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py -I/home/pco/.mujoco/mjpro150/include -I/home/pco/.local/lib/python3.5/site-packages/numpy/core/include -I/usr/include/python3.5m -c /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/gl/osmesashim.c -o /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/gl/osmesashim.o -fopenmp -w
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/lib.linux-x86_64-3.5
creating /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/lib.linux-x86_64-3.5/mujoco_py
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/cymj.o /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/temp.linux-x86_64-3.5/tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/gl/osmesashim.o -L/home/pco/.mujoco/mjpro150/bin -Wl,--enable-new-dtags,-R/home/pco/.mujoco/mjpro150/bin -lmujoco150 -lglewosmesa -lOSMesa -o /tmp/pip-build-lfrvbntl/mujoco-py/mujoco_py/generated/_pyxbld_LinuxCPUExtensionBuilder/lib.linux-x86_64-3.5/mujoco_py/cymj.cpython-35m-x86_64-linux-gnu.so -fopenmp
���[��� �[V: not found
sh: 2: [
: not found
���[��� �[V: not found
sh: 2: [
: not found
���[��� �[V: not found
sh: 2: Syntax error: "(" unexpected
���[��� �[V: not found
sh: 2: Syntax error: "(" unexpected
ERROR: Invalid activation key
Press Enter to exit ...
Failed building wheel for mujoco-py
Running setup.py clean for mujoco-py
Failed to build mujoco-py
Installing collected packages: mujoco-py
Running setup.py install for mujoco-py ...
error
Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-lfrvbntl/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-yeem0tw6-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
���[��� �[V: not found
sh: 2: [
: not found
���[��� �[V: not found
sh: 2: [
: not found
���[��� �[V: not found
sh: 2: Syntax error: "(" unexpected
���[��� �[V: not found
sh: 2: Syntax error: "(" unexpected
ERROR: Invalid activation key
Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-lfrvbntl/mujoco-py/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-yeem0tw6-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-lfrvbntl/mujoco-py/
`
I did note "ERROR: Invalid activation key", but I am able to run ./simulate from mjpro150/bin directory with no problem. Also, this error comes after the strange binary characters. I've placed copies of my mjkey.txt file in .mujoco/ as specified in mujoco-py instructions
The text was updated successfully, but these errors were encountered: