I compiled ffmpeg and somehow installed it to /usr/local/bin/bin/ffmpeg. Can I move it myself without causing...
0
Since terminal can't find it anyways, I would assume it's safe to move, but I'm not sure how that would affect other files that either rely on ffmpeg install path if they do. FWIW I used
./configure --prefix=/usr/local/bin --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64
to configure the package, then sudo make install in a separate terminal on accident, although I don't think that should make a difference. I had also removed an older ffmpeg after sudo make install but that was a repo package installed in /usr.
ffmpeg paths
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
|
show 2 more comments
0
Since terminal can't find it anyways, I would assume it's safe to move, but I'm not sure how that would affect other files that either rely on ffmpeg install path if they do. FWIW I used
./configure --prefix=/usr/local/bin --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64
to configure the package, then sudo make install in a separate terminal on accident, although I don't think that should make a difference. I had also removed an older ffmpeg after sudo make install but that was a repo package installed in /usr.
ffmpeg paths
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
2
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Since you ransudo make installin a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you getmake: *** No rule to make target 'install'. Stop.meaning nothing happened? Isffmpegactually in/usr/local/bin? If no, then yoursudo make installprobably didn't do anything as mentioned before. Also, why and where do you want to move it?
– llogan
Jan 22 at 18:39
If I recall correctly/usr/local/binis in the vanilla UbuntuPATH, so you don't need to add this directory to thePATH. Only reason I can think of that terminal does not find it is if it did not actually install to/usr/local/bin, or if you are using the same terminal session that previously executed the repoffmpeg, then installed the compiledffmpeg, but the hash index was not updated. See output ofhash. Should not show/usr/bin/ffmpegbut should show/usr/local/bin/ffmpeg. If not, then runhash -d ffmpegand try running again.
– llogan
Jan 22 at 18:49
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since runningsudo make installwould use the configuration in which--prefix=/usr/local/binwas defined. The thing I'm having trouble finding information on is movingffmpegfrom/usr/local/bin/binto/usr/local/binbecause I am assumingffmpegbeing nested in a folder is causing an issue. By the way,hashoutput:1 /bin/psand the command didn't findffmpeg.
– avisitoritseems
Jan 23 at 0:55
|
show 2 more comments
0
0
0
Since terminal can't find it anyways, I would assume it's safe to move, but I'm not sure how that would affect other files that either rely on ffmpeg install path if they do. FWIW I used
./configure --prefix=/usr/local/bin --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64
to configure the package, then sudo make install in a separate terminal on accident, although I don't think that should make a difference. I had also removed an older ffmpeg after sudo make install but that was a repo package installed in /usr.
ffmpeg paths
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
Since terminal can't find it anyways, I would assume it's safe to move, but I'm not sure how that would affect other files that either rely on ffmpeg install path if they do. FWIW I used
./configure --prefix=/usr/local/bin --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64
to configure the package, then sudo make install in a separate terminal on accident, although I don't think that should make a difference. I had also removed an older ffmpeg after sudo make install but that was a repo package installed in /usr.
ffmpeg paths
ffmpeg paths
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
asked Jan 22 at 13:41
avisitoritseemsavisitoritseems
319
319
2
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Since you ransudo make installin a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you getmake: *** No rule to make target 'install'. Stop.meaning nothing happened? Isffmpegactually in/usr/local/bin? If no, then yoursudo make installprobably didn't do anything as mentioned before. Also, why and where do you want to move it?
– llogan
Jan 22 at 18:39
If I recall correctly/usr/local/binis in the vanilla UbuntuPATH, so you don't need to add this directory to thePATH. Only reason I can think of that terminal does not find it is if it did not actually install to/usr/local/bin, or if you are using the same terminal session that previously executed the repoffmpeg, then installed the compiledffmpeg, but the hash index was not updated. See output ofhash. Should not show/usr/bin/ffmpegbut should show/usr/local/bin/ffmpeg. If not, then runhash -d ffmpegand try running again.
– llogan
Jan 22 at 18:49
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since runningsudo make installwould use the configuration in which--prefix=/usr/local/binwas defined. The thing I'm having trouble finding information on is movingffmpegfrom/usr/local/bin/binto/usr/local/binbecause I am assumingffmpegbeing nested in a folder is causing an issue. By the way,hashoutput:1 /bin/psand the command didn't findffmpeg.
– avisitoritseems
Jan 23 at 0:55
|
show 2 more comments
2
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Since you ransudo make installin a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you getmake: *** No rule to make target 'install'. Stop.meaning nothing happened? Isffmpegactually in/usr/local/bin? If no, then yoursudo make installprobably didn't do anything as mentioned before. Also, why and where do you want to move it?
– llogan
Jan 22 at 18:39
If I recall correctly/usr/local/binis in the vanilla UbuntuPATH, so you don't need to add this directory to thePATH. Only reason I can think of that terminal does not find it is if it did not actually install to/usr/local/bin, or if you are using the same terminal session that previously executed the repoffmpeg, then installed the compiledffmpeg, but the hash index was not updated. See output ofhash. Should not show/usr/bin/ffmpegbut should show/usr/local/bin/ffmpeg. If not, then runhash -d ffmpegand try running again.
– llogan
Jan 22 at 18:49
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since runningsudo make installwould use the configuration in which--prefix=/usr/local/binwas defined. The thing I'm having trouble finding information on is movingffmpegfrom/usr/local/bin/binto/usr/local/binbecause I am assumingffmpegbeing nested in a folder is causing an issue. By the way,hashoutput:1 /bin/psand the command didn't findffmpeg.
– avisitoritseems
Jan 23 at 0:55
2
2
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Since you ran
sudo make install in a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you get make: *** No rule to make target 'install'. Stop. meaning nothing happened? Is ffmpeg actually in /usr/local/bin? If no, then your sudo make install probably didn't do anything as mentioned before. Also, why and where do you want to move it?– llogan
Jan 22 at 18:39
Since you ran
sudo make install in a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you get make: *** No rule to make target 'install'. Stop. meaning nothing happened? Is ffmpeg actually in /usr/local/bin? If no, then your sudo make install probably didn't do anything as mentioned before. Also, why and where do you want to move it?– llogan
Jan 22 at 18:39
If I recall correctly
/usr/local/bin is in the vanilla Ubuntu PATH, so you don't need to add this directory to the PATH. Only reason I can think of that terminal does not find it is if it did not actually install to /usr/local/bin, or if you are using the same terminal session that previously executed the repo ffmpeg, then installed the compiled ffmpeg, but the hash index was not updated. See output of hash. Should not show /usr/bin/ffmpeg but should show /usr/local/bin/ffmpeg. If not, then run hash -d ffmpeg and try running again.– llogan
Jan 22 at 18:49
If I recall correctly
/usr/local/bin is in the vanilla Ubuntu PATH, so you don't need to add this directory to the PATH. Only reason I can think of that terminal does not find it is if it did not actually install to /usr/local/bin, or if you are using the same terminal session that previously executed the repo ffmpeg, then installed the compiled ffmpeg, but the hash index was not updated. See output of hash. Should not show /usr/bin/ffmpeg but should show /usr/local/bin/ffmpeg. If not, then run hash -d ffmpeg and try running again.– llogan
Jan 22 at 18:49
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since running
sudo make install would use the configuration in which --prefix=/usr/local/bin was defined. The thing I'm having trouble finding information on is moving ffmpeg from /usr/local/bin/bin to /usr/local/bin because I am assuming ffmpeg being nested in a folder is causing an issue. By the way, hash output: 1 /bin/ps and the command didn't find ffmpeg.– avisitoritseems
Jan 23 at 0:55
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since running
sudo make install would use the configuration in which --prefix=/usr/local/bin was defined. The thing I'm having trouble finding information on is moving ffmpeg from /usr/local/bin/bin to /usr/local/bin because I am assuming ffmpeg being nested in a folder is causing an issue. By the way, hash output: 1 /bin/ps and the command didn't find ffmpeg.– avisitoritseems
Jan 23 at 0:55
|
show 2 more comments
1 Answer
1
active
oldest
votes
0
Appreciate the help from the comments, turns out I did not need to edit my PATH nor do anything intensive.
sudo mv /usr/local/bin/bin/ffmpeg /usr/local/bin
worked, and I did move the other file in there that I can't recall the name of.
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111964%2fi-compiled-ffmpeg-and-somehow-installed-it-to-usr-local-bin-bin-ffmpeg-can-i-m%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Appreciate the help from the comments, turns out I did not need to edit my PATH nor do anything intensive.
sudo mv /usr/local/bin/bin/ffmpeg /usr/local/bin
worked, and I did move the other file in there that I can't recall the name of.
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
add a comment |
0
Appreciate the help from the comments, turns out I did not need to edit my PATH nor do anything intensive.
sudo mv /usr/local/bin/bin/ffmpeg /usr/local/bin
worked, and I did move the other file in there that I can't recall the name of.
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
add a comment |
0
0
0
Appreciate the help from the comments, turns out I did not need to edit my PATH nor do anything intensive.
sudo mv /usr/local/bin/bin/ffmpeg /usr/local/bin
worked, and I did move the other file in there that I can't recall the name of.
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
Appreciate the help from the comments, turns out I did not need to edit my PATH nor do anything intensive.
sudo mv /usr/local/bin/bin/ffmpeg /usr/local/bin
worked, and I did move the other file in there that I can't recall the name of.
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
answered Jan 27 at 3:41
avisitoritseemsavisitoritseems
319
319
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111964%2fi-compiled-ffmpeg-and-somehow-installed-it-to-usr-local-bin-bin-ffmpeg-can-i-m%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Seems like an XY problem. The problem you SHOULD be asking about is "terminal can't find it" which is very easy to fix.
– user535733
Jan 22 at 15:08
Since you ran
sudo make installin a different terminal, and therefore possibly in a different directory, did it actually execute properly? Or did you getmake: *** No rule to make target 'install'. Stop.meaning nothing happened? Isffmpegactually in/usr/local/bin? If no, then yoursudo make installprobably didn't do anything as mentioned before. Also, why and where do you want to move it?– llogan
Jan 22 at 18:39
If I recall correctly
/usr/local/binis in the vanilla UbuntuPATH, so you don't need to add this directory to thePATH. Only reason I can think of that terminal does not find it is if it did not actually install to/usr/local/bin, or if you are using the same terminal session that previously executed the repoffmpeg, then installed the compiledffmpeg, but the hash index was not updated. See output ofhash. Should not show/usr/bin/ffmpegbut should show/usr/local/bin/ffmpeg. If not, then runhash -d ffmpegand try running again.– llogan
Jan 22 at 18:49
@user535733 - thanks for that link, that should solve it; I'm going to check where ffmpeg's default path should be and put it there.
– avisitoritseems
Jan 23 at 0:41
@llogan - it executed without error, and it along with its requisite files are located in /usr/local/bin. I've been looking and I believe that shouldn't have actually caused an error using different terminals, since running
sudo make installwould use the configuration in which--prefix=/usr/local/binwas defined. The thing I'm having trouble finding information on is movingffmpegfrom/usr/local/bin/binto/usr/local/binbecause I am assumingffmpegbeing nested in a folder is causing an issue. By the way,hashoutput:1 /bin/psand the command didn't findffmpeg.– avisitoritseems
Jan 23 at 0:55