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







share|improve this question


















  • 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 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













  • @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
















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







share|improve this question


















  • 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 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













  • @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














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







share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 22 at 13:41









avisitoritseemsavisitoritseems

10110




10110








  • 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 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













  • @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














  • 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 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













  • @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








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










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.






share|improve this answer























    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


















    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.






    share|improve this answer




























      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.






      share|improve this answer


























        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.






        share|improve this answer













        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 27 at 3:41









        avisitoritseemsavisitoritseems

        10110




        10110






























            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














            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





















































            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







            -

            Popular posts from this blog

            How to change which sound is reproduced for terminal bell?

            Image
            3 Recently upgrade to 18.10 from 18.04, and using the terminal is becoming annoying: the new alert sound is a drip ( /usr/share/sounds/gnome/default/alerts/drip.ogg ), and the previous one is still located at ( /usr/share/sounds/ubuntu/stereo/bell.ogg ). My issue is that at the gnome-terminal, when autocompleting or pressing left BOTH sounds are reproduced, at the same time. I want to just have ubuntu/stereo/bell.ogg active, not both . At the moment I have been only able to reduce the volume of the alerts (but still both are played), or turn the alerts down (but I dislike both "solutions"). gnome-terminal 18.10 teminal-bell share | improve this question
            Read more

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Image
            up vote 5 down vote favorite 2 I would like to make it so that the vertical space below the title of each chapter is the same when using the Bjornstrup package (i.e. so that the descenders do not affect the spacing - as shown by the red arrow in the picture below). I think I'm fairly happy with the spacing around "A chapter", so I'd really like titles without descenders (e.g. "Contents") to have the same vertical spacing as "A chapter" below the title. I would also like to remove the large "0" in the contents title. Any help appreciated, as always. documentclass[11pt,a4paper]{book} % Packages[![enter image description here][1]][1] usepackage[left=3.5cm, right=3.5cm, top=4.3cm, bottom=4.25cm]{geometry} usepackage[utf8]{inputenc} usepackage{libertine} usepackage[libertine]{newtx
            Read more

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Image
            0 I want to add Tabulator js to my java project. I added tabulator.min.js, tabulator.min.css to resources folder. After that added to my html page these dependencies as recommending in readme.md. <link rel="stylesheet" th:href="@{/css/tabulator.min.css}"> <script type="text/javascript" th:src="@{/js/tabulator.min.js}"></script> Now my tables view all elements, that I have in the html page, but not correct. In the documentation of Tabulator is example how to create header and table, var table = new Tabulator("#example-table", { columns:[ {title:"Name", field:"name", sorter:"string", width:200, editor:true}, {title:"Age", field:"age", sorter:"
            Read more