Cannot open executable file (shared library)? [closed]
I compiled some software from GitHub and I tried to run it, but I can't.
Any ideas why it is not working?
executable
edited Dec 27 '18 at 11:28
Thomas
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
closed as unclear what you're asking by Thomas, guntbert, Zanna, Eric Carvalho, George Udosen Dec 31 '18 at 20:27
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I compiled some software from GitHub and I tried to run it, but I can't.
Any ideas why it is not working?
executable
edited Dec 27 '18 at 11:28
Thomas
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
closed as unclear what you're asking by Thomas, guntbert, Zanna, Eric Carvalho, George Udosen Dec 31 '18 at 20:27
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40
add a comment |
I compiled some software from GitHub and I tried to run it, but I can't.
Any ideas why it is not working?
executable
edited Dec 27 '18 at 11:28
Thomas
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
I compiled some software from GitHub and I tried to run it, but I can't.
Any ideas why it is not working?
executable
executable
edited Dec 27 '18 at 11:28
Thomas
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
edited Dec 27 '18 at 11:28
Thomas
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
edited Dec 27 '18 at 11:28
Thomas
3,59381527
edited Dec 27 '18 at 11:28
Thomas
3,59381527
edited Dec 27 '18 at 11:28
Thomas
3,59381527
3,59381527
asked Dec 27 '18 at 11:21
igniss.igniss.
61
asked Dec 27 '18 at 11:21
igniss.igniss.
61
asked Dec 27 '18 at 11:21
igniss.igniss.
61
61
closed as unclear what you're asking by Thomas, guntbert, Zanna, Eric Carvalho, George Udosen Dec 31 '18 at 20:27
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Thomas, guntbert, Zanna, Eric Carvalho, George Udosen Dec 31 '18 at 20:27
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40
add a comment |
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40
add a comment |
1 Answer
1
active
oldest
votes
Compiling from github source code is more complicated than simple installation. Your package is available for Ubuntu 14.04 and 16.04 according to the vendor. To see if it is available for a different Ubuntu version use this command:
$ apt search aseprite
Sorting... Done
Full Text Search... Done
aseprite/xenial 1.0.9+ds-3.2 amd64
sprite and pixel art editor
To do a "dry-run" installation (simulated installation) use this command:
$ sudo apt install -s aseprite
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
The following NEW packages will be installed:
aseprite liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Inst aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
Conf liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Conf aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
As you can see the aseprite application is dependent on many other libraries that need to be installed. I suspect when you compile manually some of these libraries are missing.
To do a real installation use:
sudo apt install aseprite
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Compiling from github source code is more complicated than simple installation. Your package is available for Ubuntu 14.04 and 16.04 according to the vendor. To see if it is available for a different Ubuntu version use this command:
$ apt search aseprite
Sorting... Done
Full Text Search... Done
aseprite/xenial 1.0.9+ds-3.2 amd64
sprite and pixel art editor
To do a "dry-run" installation (simulated installation) use this command:
$ sudo apt install -s aseprite
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
The following NEW packages will be installed:
aseprite liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Inst aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
Conf liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Conf aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
As you can see the aseprite application is dependent on many other libraries that need to be installed. I suspect when you compile manually some of these libraries are missing.
To do a real installation use:
sudo apt install aseprite
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
add a comment |
Compiling from github source code is more complicated than simple installation. Your package is available for Ubuntu 14.04 and 16.04 according to the vendor. To see if it is available for a different Ubuntu version use this command:
$ apt search aseprite
Sorting... Done
Full Text Search... Done
aseprite/xenial 1.0.9+ds-3.2 amd64
sprite and pixel art editor
To do a "dry-run" installation (simulated installation) use this command:
$ sudo apt install -s aseprite
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
The following NEW packages will be installed:
aseprite liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Inst aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
Conf liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Conf aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
As you can see the aseprite application is dependent on many other libraries that need to be installed. I suspect when you compile manually some of these libraries are missing.
To do a real installation use:
sudo apt install aseprite
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
add a comment |
Compiling from github source code is more complicated than simple installation. Your package is available for Ubuntu 14.04 and 16.04 according to the vendor. To see if it is available for a different Ubuntu version use this command:
$ apt search aseprite
Sorting... Done
Full Text Search... Done
aseprite/xenial 1.0.9+ds-3.2 amd64
sprite and pixel art editor
To do a "dry-run" installation (simulated installation) use this command:
$ sudo apt install -s aseprite
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
The following NEW packages will be installed:
aseprite liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Inst aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
Conf liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Conf aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
As you can see the aseprite application is dependent on many other libraries that need to be installed. I suspect when you compile manually some of these libraries are missing.
To do a real installation use:
sudo apt install aseprite
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
Compiling from github source code is more complicated than simple installation. Your package is available for Ubuntu 14.04 and 16.04 according to the vendor. To see if it is available for a different Ubuntu version use this command:
$ apt search aseprite
Sorting... Done
Full Text Search... Done
aseprite/xenial 1.0.9+ds-3.2 amd64
sprite and pixel art editor
To do a "dry-run" installation (simulated installation) use this command:
$ sudo apt install -s aseprite
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
The following NEW packages will be installed:
aseprite liballegro4.4 libloadpng4.4 libtinyxml2.6.2v5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Inst liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Inst libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Inst aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
Conf liballegro4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libloadpng4.4 (2:4.4.2-7 Ubuntu:16.04/xenial [amd64])
Conf libtinyxml2.6.2v5 (2.6.2-3 Ubuntu:16.04/xenial [amd64])
Conf aseprite (1.0.9+ds-3.2 Ubuntu:16.04/xenial [amd64])
As you can see the aseprite application is dependent on many other libraries that need to be installed. I suspect when you compile manually some of these libraries are missing.
To do a real installation use:
sudo apt install aseprite
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
answered Dec 27 '18 at 12:36
WinEunuuchs2UnixWinEunuuchs2Unix
44.6k1079169
44.6k1079169
add a comment |
add a comment |
The repo would tell you better or the readme file!
– George Udosen
Dec 27 '18 at 11:28
It would help a lot if you told what and how you did to build your software. Maybe try to run it from terminal to get the full error text.
– Soren A
Dec 27 '18 at 11:35
See Impossible to launch graphic executables in nautilus
– steeldriver
Dec 27 '18 at 11:40