Closed MLXXXp closed 5 years ago
Hi
Have you tried doing a pip install wheel in the virtual environment? My impression from reading the logs is that you may not have that installed (hence the wheel building that fails). You may also need to upgrade pip to the latest version (also inside the virtual env) or even install the python dev package.
Would appreciate you trying the above (maybe even step by step) and trying to rerun the installer afterward to see what solves the problem. It is indeed possible that I take a certain package for granted that isn't there on every system.
Problem solved!
Upgrading pip to the latest version or installing wheel, in the virtual environment, didn't help.
It turns out that two Ubuntu packages were missing.
When I saw the error about installing the development version of Python, I verified that package python‑dev had been installed. I didn't clue in to the fact that I actually needed package python3-dev
Once python3-dev was installed, I got the message:
checking for DBUS... no
configure: error: Package requirements (dbus-1 >= 1.8) were not met:
No package 'dbus-1' found
This was solved by installing package libdbus-1-dev
I have three systems running Ubuntu 16.04 with Unity 7, all set up fairly similarly. On the first system, install.sh runs without errors and the indicator works fine using run.sh. On the other two systems, install.sh fails in the same way. The last line of console output is:
./install.sh: line 6: vext: command not found
(so this may be a duplicate of issue #63)Between the working system and the failing ones, the install.sh output is nearly identical up until the line:
Running setup.py install for dbus-python ...
where the line ends withdone
for the good system anderror
for the failing ones.After this error, the output contains some detailed info about the problem. However, I'm not familiar enough with Python to figure out what the problem is, especially when using a virtualenv.
I've attached 3 files containing the console output from running install.sh on each system:
install_out_sys1_good.txt (successful build) install_out_sys2_fail.txt install_out_sys3_fail.txt