Building a file in Linux
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I am a Windows user but I need to use a Linux tool. I am using Ubuntu. The tool's website here provided a file named: build-x86-64.sh
which I installed it. It then says all what you need is to run: % ./build-x86-64.sh
. I tried sudo ./build-x86-64.sh
. However, I get this error from Linux:
sudo: ./build-x86-64.sh: command not found
Note that I am in the right directory where I saved the .sh
file. I also installed all the per-requisites:
autoconf
automake
libtool
pkg-config
gcc
Please, can you point to me what's wrong?
tls
migrated from security.stackexchange.com Apr 28 at 16:33
This question came from our site for information security professionals.
add a comment |Â
up vote
0
down vote
favorite
I am a Windows user but I need to use a Linux tool. I am using Ubuntu. The tool's website here provided a file named: build-x86-64.sh
which I installed it. It then says all what you need is to run: % ./build-x86-64.sh
. I tried sudo ./build-x86-64.sh
. However, I get this error from Linux:
sudo: ./build-x86-64.sh: command not found
Note that I am in the right directory where I saved the .sh
file. I also installed all the per-requisites:
autoconf
automake
libtool
pkg-config
gcc
Please, can you point to me what's wrong?
tls
migrated from security.stackexchange.com Apr 28 at 16:33
This question came from our site for information security professionals.
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am a Windows user but I need to use a Linux tool. I am using Ubuntu. The tool's website here provided a file named: build-x86-64.sh
which I installed it. It then says all what you need is to run: % ./build-x86-64.sh
. I tried sudo ./build-x86-64.sh
. However, I get this error from Linux:
sudo: ./build-x86-64.sh: command not found
Note that I am in the right directory where I saved the .sh
file. I also installed all the per-requisites:
autoconf
automake
libtool
pkg-config
gcc
Please, can you point to me what's wrong?
tls
I am a Windows user but I need to use a Linux tool. I am using Ubuntu. The tool's website here provided a file named: build-x86-64.sh
which I installed it. It then says all what you need is to run: % ./build-x86-64.sh
. I tried sudo ./build-x86-64.sh
. However, I get this error from Linux:
sudo: ./build-x86-64.sh: command not found
Note that I am in the right directory where I saved the .sh
file. I also installed all the per-requisites:
autoconf
automake
libtool
pkg-config
gcc
Please, can you point to me what's wrong?
tls
asked Apr 28 at 6:36
None
migrated from security.stackexchange.com Apr 28 at 16:33
This question came from our site for information security professionals.
migrated from security.stackexchange.com Apr 28 at 16:33
This question came from our site for information security professionals.
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52
add a comment |Â
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
When using sudo
to run a script using relative path syntax, it appears that many different error messages get hidden behind that "command not found" error message. I'd suggest re-running without the sudo
to see what the actual error is.
Likely issues:
- My guess is the .sh file doesn't have the executable bit set (i.e., the OS hasn't been told it's a program). Try
chmod a+x build-x86-64.sh
from the same directory, to fix this. This should only need to be done once, and you may wish to look up "executable bit" at some point. - Maybe the file isn't where you think it is? But, you say you're already in the same directory, so it should be fine...
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
add a comment |Â
up vote
1
down vote
- check your user running:
whoami
- check if you can execute the bash script running:
ls -la build-x86-64.sh
- check if your user can call sudo running:
sudo -l -U <whoami-output>
- check if your shell is able to run sudo running:
sudo whoami
So:
- If the output of the point 1 or 4 is
root
the problem is relative at the permission about execution of build-x86-64.sh file, change it running :sudo chmod 744 build-x86-64.sh
and then run againsudo ./build-x86-64.sh
- If the output of point 3 say you are able to run sudo , you have to put the directory where the file
build-x86-64.sh
is in the sudoers secure_path editing the/etc/sudoers
file by running :sudo visudo
and adding the /path-where-is-your-file.sh as explained here. Be careful, editing that file can compromise the security of your device.
Hope it help ;)
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
When using sudo
to run a script using relative path syntax, it appears that many different error messages get hidden behind that "command not found" error message. I'd suggest re-running without the sudo
to see what the actual error is.
Likely issues:
- My guess is the .sh file doesn't have the executable bit set (i.e., the OS hasn't been told it's a program). Try
chmod a+x build-x86-64.sh
from the same directory, to fix this. This should only need to be done once, and you may wish to look up "executable bit" at some point. - Maybe the file isn't where you think it is? But, you say you're already in the same directory, so it should be fine...
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
add a comment |Â
up vote
1
down vote
When using sudo
to run a script using relative path syntax, it appears that many different error messages get hidden behind that "command not found" error message. I'd suggest re-running without the sudo
to see what the actual error is.
Likely issues:
- My guess is the .sh file doesn't have the executable bit set (i.e., the OS hasn't been told it's a program). Try
chmod a+x build-x86-64.sh
from the same directory, to fix this. This should only need to be done once, and you may wish to look up "executable bit" at some point. - Maybe the file isn't where you think it is? But, you say you're already in the same directory, so it should be fine...
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
add a comment |Â
up vote
1
down vote
up vote
1
down vote
When using sudo
to run a script using relative path syntax, it appears that many different error messages get hidden behind that "command not found" error message. I'd suggest re-running without the sudo
to see what the actual error is.
Likely issues:
- My guess is the .sh file doesn't have the executable bit set (i.e., the OS hasn't been told it's a program). Try
chmod a+x build-x86-64.sh
from the same directory, to fix this. This should only need to be done once, and you may wish to look up "executable bit" at some point. - Maybe the file isn't where you think it is? But, you say you're already in the same directory, so it should be fine...
When using sudo
to run a script using relative path syntax, it appears that many different error messages get hidden behind that "command not found" error message. I'd suggest re-running without the sudo
to see what the actual error is.
Likely issues:
- My guess is the .sh file doesn't have the executable bit set (i.e., the OS hasn't been told it's a program). Try
chmod a+x build-x86-64.sh
from the same directory, to fix this. This should only need to be done once, and you may wish to look up "executable bit" at some point. - Maybe the file isn't where you think it is? But, you say you're already in the same directory, so it should be fine...
answered Apr 28 at 21:10
Ethan Kaminski
1412
1412
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
add a comment |Â
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
It is likely/will be #1. The link is missing instructions on making the file executable.
â Rinzwind
Apr 28 at 21:15
add a comment |Â
up vote
1
down vote
- check your user running:
whoami
- check if you can execute the bash script running:
ls -la build-x86-64.sh
- check if your user can call sudo running:
sudo -l -U <whoami-output>
- check if your shell is able to run sudo running:
sudo whoami
So:
- If the output of the point 1 or 4 is
root
the problem is relative at the permission about execution of build-x86-64.sh file, change it running :sudo chmod 744 build-x86-64.sh
and then run againsudo ./build-x86-64.sh
- If the output of point 3 say you are able to run sudo , you have to put the directory where the file
build-x86-64.sh
is in the sudoers secure_path editing the/etc/sudoers
file by running :sudo visudo
and adding the /path-where-is-your-file.sh as explained here. Be careful, editing that file can compromise the security of your device.
Hope it help ;)
add a comment |Â
up vote
1
down vote
- check your user running:
whoami
- check if you can execute the bash script running:
ls -la build-x86-64.sh
- check if your user can call sudo running:
sudo -l -U <whoami-output>
- check if your shell is able to run sudo running:
sudo whoami
So:
- If the output of the point 1 or 4 is
root
the problem is relative at the permission about execution of build-x86-64.sh file, change it running :sudo chmod 744 build-x86-64.sh
and then run againsudo ./build-x86-64.sh
- If the output of point 3 say you are able to run sudo , you have to put the directory where the file
build-x86-64.sh
is in the sudoers secure_path editing the/etc/sudoers
file by running :sudo visudo
and adding the /path-where-is-your-file.sh as explained here. Be careful, editing that file can compromise the security of your device.
Hope it help ;)
add a comment |Â
up vote
1
down vote
up vote
1
down vote
- check your user running:
whoami
- check if you can execute the bash script running:
ls -la build-x86-64.sh
- check if your user can call sudo running:
sudo -l -U <whoami-output>
- check if your shell is able to run sudo running:
sudo whoami
So:
- If the output of the point 1 or 4 is
root
the problem is relative at the permission about execution of build-x86-64.sh file, change it running :sudo chmod 744 build-x86-64.sh
and then run againsudo ./build-x86-64.sh
- If the output of point 3 say you are able to run sudo , you have to put the directory where the file
build-x86-64.sh
is in the sudoers secure_path editing the/etc/sudoers
file by running :sudo visudo
and adding the /path-where-is-your-file.sh as explained here. Be careful, editing that file can compromise the security of your device.
Hope it help ;)
- check your user running:
whoami
- check if you can execute the bash script running:
ls -la build-x86-64.sh
- check if your user can call sudo running:
sudo -l -U <whoami-output>
- check if your shell is able to run sudo running:
sudo whoami
So:
- If the output of the point 1 or 4 is
root
the problem is relative at the permission about execution of build-x86-64.sh file, change it running :sudo chmod 744 build-x86-64.sh
and then run againsudo ./build-x86-64.sh
- If the output of point 3 say you are able to run sudo , you have to put the directory where the file
build-x86-64.sh
is in the sudoers secure_path editing the/etc/sudoers
file by running :sudo visudo
and adding the /path-where-is-your-file.sh as explained here. Be careful, editing that file can compromise the security of your device.
Hope it help ;)
answered Apr 29 at 1:40
![](https://lh6.googleusercontent.com/-zysTsphgh80/AAAAAAAAAAI/AAAAAAAAACM/Q2h-OaaX0mA/photo.jpg?sz=32)
![](https://lh6.googleusercontent.com/-zysTsphgh80/AAAAAAAAAAI/AAAAAAAAACM/Q2h-OaaX0mA/photo.jpg?sz=32)
Mike D3ViD Tyson
112
112
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029312%2fbuilding-a-file-in-linux%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Also, downloaded files do not have the executable bit set. chmod +x file should make it easier to be executed.
â SmokeDispenser
Apr 28 at 7:52