How to run 32-bit app in Ubuntu 64-bit?












113














I installed Ubuntu 14.04 and the current Android development SDK, which contains 32-bit executables. I found that I cannot run those 32-bit binaries. Trying to start them from bash gives me an error:



$ ./adb
bash: ./adb: No such file or directory


It is there though:



$ ls -al ./adb
-rwxrwxrwx 1 thomas thomas 1231255 Jan 17 13:31 ./adb
$ file ./adb
./adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped. Same symptom for all the other 32-bit tools in the Android SDK.


In olden days one could just install 32-bit libraries on 64-bit Ubuntu to get 32-bit support, but that does not seem to work anymore.



How do I run 32-bit apps on a 64-bit Ubuntu 14.04?










share|improve this question
























  • stackoverflow.com/a/19524010/1778421
    – Alex P.
    Jun 1 '18 at 22:36
















113














I installed Ubuntu 14.04 and the current Android development SDK, which contains 32-bit executables. I found that I cannot run those 32-bit binaries. Trying to start them from bash gives me an error:



$ ./adb
bash: ./adb: No such file or directory


It is there though:



$ ls -al ./adb
-rwxrwxrwx 1 thomas thomas 1231255 Jan 17 13:31 ./adb
$ file ./adb
./adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped. Same symptom for all the other 32-bit tools in the Android SDK.


In olden days one could just install 32-bit libraries on 64-bit Ubuntu to get 32-bit support, but that does not seem to work anymore.



How do I run 32-bit apps on a 64-bit Ubuntu 14.04?










share|improve this question
























  • stackoverflow.com/a/19524010/1778421
    – Alex P.
    Jun 1 '18 at 22:36














113












113








113


65





I installed Ubuntu 14.04 and the current Android development SDK, which contains 32-bit executables. I found that I cannot run those 32-bit binaries. Trying to start them from bash gives me an error:



$ ./adb
bash: ./adb: No such file or directory


It is there though:



$ ls -al ./adb
-rwxrwxrwx 1 thomas thomas 1231255 Jan 17 13:31 ./adb
$ file ./adb
./adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped. Same symptom for all the other 32-bit tools in the Android SDK.


In olden days one could just install 32-bit libraries on 64-bit Ubuntu to get 32-bit support, but that does not seem to work anymore.



How do I run 32-bit apps on a 64-bit Ubuntu 14.04?










share|improve this question















I installed Ubuntu 14.04 and the current Android development SDK, which contains 32-bit executables. I found that I cannot run those 32-bit binaries. Trying to start them from bash gives me an error:



$ ./adb
bash: ./adb: No such file or directory


It is there though:



$ ls -al ./adb
-rwxrwxrwx 1 thomas thomas 1231255 Jan 17 13:31 ./adb
$ file ./adb
./adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped. Same symptom for all the other 32-bit tools in the Android SDK.


In olden days one could just install 32-bit libraries on 64-bit Ubuntu to get 32-bit support, but that does not seem to work anymore.



How do I run 32-bit apps on a 64-bit Ubuntu 14.04?







64-bit 32-bit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 28 '17 at 6:03









wjandrea

8,47842259




8,47842259










asked Apr 24 '14 at 7:29









Thomas StuefeThomas Stuefe

668266




668266












  • stackoverflow.com/a/19524010/1778421
    – Alex P.
    Jun 1 '18 at 22:36


















  • stackoverflow.com/a/19524010/1778421
    – Alex P.
    Jun 1 '18 at 22:36
















stackoverflow.com/a/19524010/1778421
– Alex P.
Jun 1 '18 at 22:36




stackoverflow.com/a/19524010/1778421
– Alex P.
Jun 1 '18 at 22:36










4 Answers
4






active

oldest

votes


















165














To run a 32-bit executable file on a 64-bit multi-architecture Ubuntu system, you have to add the i386 architecture and install the three library packages libc6:i386, libncurses5:i386, and libstdc++6:i386:



sudo dpkg --add-architecture i386


Or if you are using Ubuntu 12.04 LTS (Precise Pangolin) or below, use this:



echo "foreign-architecture i386" > /etc/dpkg/dpkg.cfg.d/multiarch


Then:



sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


If fails, do also



sudo apt-get install multiarch-support


After these steps, you should be able to run the 32-bit application:



./example32bitprogram





share|improve this answer























  • @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
    – Marcel
    May 22 '14 at 21:33






  • 1




    It executes the 32bit adb binary file which was present in the current directory.
    – Avinash Raj
    May 23 '14 at 1:05






  • 1




    to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
    – Chris Betti
    May 23 '14 at 19:09










  • I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
    – Fredrick Gauss
    Jun 4 '14 at 6:09










  • @FredrickGauss get into here.
    – Avinash Raj
    Jun 4 '14 at 6:13



















7














"No such file or directory" may appaear when you have your binary, but it lacks some libraries. If you install build-essential package, you will have ldd command available. This command ldd ./adb | grep not will show you what libraries are missing. Just install these libraries in i386 arch with apt. Like this: apt-get install libmissing:i386
Beware, some buggy packages will try to delete 64bit version firs.






share|improve this answer





















  • Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
    – Thomas Stuefe
    Apr 24 '14 at 12:30





















4














And if you want to use "adb" there is a package for it:



sudo apt-get install android-tools-adb


And about 32-bit libraries - only:



sudo apt-add-architecture i386


will be enough.






share|improve this answer























  • Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
    – Thomas Stuefe
    Apr 24 '14 at 12:36










  • Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
    – aastefanov
    Apr 24 '14 at 12:44



















2














Additionally to the excellent answer of Zanna and Avinash Raj I had to install gcc-multilib as well:



sudo apt-get install gcc-multilib


Possibly this is because I wanted to run an old gcc version on 64bit.






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%2f454253%2fhow-to-run-32-bit-app-in-ubuntu-64-bit%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    165














    To run a 32-bit executable file on a 64-bit multi-architecture Ubuntu system, you have to add the i386 architecture and install the three library packages libc6:i386, libncurses5:i386, and libstdc++6:i386:



    sudo dpkg --add-architecture i386


    Or if you are using Ubuntu 12.04 LTS (Precise Pangolin) or below, use this:



    echo "foreign-architecture i386" > /etc/dpkg/dpkg.cfg.d/multiarch


    Then:



    sudo apt-get update
    sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


    If fails, do also



    sudo apt-get install multiarch-support


    After these steps, you should be able to run the 32-bit application:



    ./example32bitprogram





    share|improve this answer























    • @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
      – Marcel
      May 22 '14 at 21:33






    • 1




      It executes the 32bit adb binary file which was present in the current directory.
      – Avinash Raj
      May 23 '14 at 1:05






    • 1




      to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
      – Chris Betti
      May 23 '14 at 19:09










    • I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
      – Fredrick Gauss
      Jun 4 '14 at 6:09










    • @FredrickGauss get into here.
      – Avinash Raj
      Jun 4 '14 at 6:13
















    165














    To run a 32-bit executable file on a 64-bit multi-architecture Ubuntu system, you have to add the i386 architecture and install the three library packages libc6:i386, libncurses5:i386, and libstdc++6:i386:



    sudo dpkg --add-architecture i386


    Or if you are using Ubuntu 12.04 LTS (Precise Pangolin) or below, use this:



    echo "foreign-architecture i386" > /etc/dpkg/dpkg.cfg.d/multiarch


    Then:



    sudo apt-get update
    sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


    If fails, do also



    sudo apt-get install multiarch-support


    After these steps, you should be able to run the 32-bit application:



    ./example32bitprogram





    share|improve this answer























    • @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
      – Marcel
      May 22 '14 at 21:33






    • 1




      It executes the 32bit adb binary file which was present in the current directory.
      – Avinash Raj
      May 23 '14 at 1:05






    • 1




      to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
      – Chris Betti
      May 23 '14 at 19:09










    • I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
      – Fredrick Gauss
      Jun 4 '14 at 6:09










    • @FredrickGauss get into here.
      – Avinash Raj
      Jun 4 '14 at 6:13














    165












    165








    165






    To run a 32-bit executable file on a 64-bit multi-architecture Ubuntu system, you have to add the i386 architecture and install the three library packages libc6:i386, libncurses5:i386, and libstdc++6:i386:



    sudo dpkg --add-architecture i386


    Or if you are using Ubuntu 12.04 LTS (Precise Pangolin) or below, use this:



    echo "foreign-architecture i386" > /etc/dpkg/dpkg.cfg.d/multiarch


    Then:



    sudo apt-get update
    sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


    If fails, do also



    sudo apt-get install multiarch-support


    After these steps, you should be able to run the 32-bit application:



    ./example32bitprogram





    share|improve this answer














    To run a 32-bit executable file on a 64-bit multi-architecture Ubuntu system, you have to add the i386 architecture and install the three library packages libc6:i386, libncurses5:i386, and libstdc++6:i386:



    sudo dpkg --add-architecture i386


    Or if you are using Ubuntu 12.04 LTS (Precise Pangolin) or below, use this:



    echo "foreign-architecture i386" > /etc/dpkg/dpkg.cfg.d/multiarch


    Then:



    sudo apt-get update
    sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386


    If fails, do also



    sudo apt-get install multiarch-support


    After these steps, you should be able to run the 32-bit application:



    ./example32bitprogram






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jan 30 '17 at 15:54









    Zanna

    50.3k13133241




    50.3k13133241










    answered Apr 24 '14 at 7:31









    Avinash RajAvinash Raj

    51.3k41166215




    51.3k41166215












    • @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
      – Marcel
      May 22 '14 at 21:33






    • 1




      It executes the 32bit adb binary file which was present in the current directory.
      – Avinash Raj
      May 23 '14 at 1:05






    • 1




      to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
      – Chris Betti
      May 23 '14 at 19:09










    • I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
      – Fredrick Gauss
      Jun 4 '14 at 6:09










    • @FredrickGauss get into here.
      – Avinash Raj
      Jun 4 '14 at 6:13


















    • @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
      – Marcel
      May 22 '14 at 21:33






    • 1




      It executes the 32bit adb binary file which was present in the current directory.
      – Avinash Raj
      May 23 '14 at 1:05






    • 1




      to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
      – Chris Betti
      May 23 '14 at 19:09










    • I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
      – Fredrick Gauss
      Jun 4 '14 at 6:09










    • @FredrickGauss get into here.
      – Avinash Raj
      Jun 4 '14 at 6:13
















    @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
    – Marcel
    May 22 '14 at 21:33




    @AvinashRaj This helped me out! However, what is the last command "sudo ./adb" supposed to do actually?
    – Marcel
    May 22 '14 at 21:33




    1




    1




    It executes the 32bit adb binary file which was present in the current directory.
    – Avinash Raj
    May 23 '14 at 1:05




    It executes the 32bit adb binary file which was present in the current directory.
    – Avinash Raj
    May 23 '14 at 1:05




    1




    1




    to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
    – Chris Betti
    May 23 '14 at 19:09




    to get aapt working on Ubuntu 14.04, I had to install lib32z1 as well, but noticed it pulled in libc6-i386 (distinction, notice the hyphen, not the colon).
    – Chris Betti
    May 23 '14 at 19:09












    I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
    – Fredrick Gauss
    Jun 4 '14 at 6:09




    I did your steps, libc6:i386, libncurses5:i386, libstdc++6:i386 are newest version and set to manually installed. But after that it says: "Soma packages could not be installed.This may mean you have requested impossible situation or you are using unstable distribution ..." and unmet dependancies: libstdc++6-4.4-dev:i386 depends g++-4.4:i386(wont be installed). conflicts: libstdc++6-4.4-dbg:i386 ... and other conflicts about libstdc++6-4.4/6/7 etc. What is wrong or should i leave it as it is now?
    – Fredrick Gauss
    Jun 4 '14 at 6:09












    @FredrickGauss get into here.
    – Avinash Raj
    Jun 4 '14 at 6:13




    @FredrickGauss get into here.
    – Avinash Raj
    Jun 4 '14 at 6:13













    7














    "No such file or directory" may appaear when you have your binary, but it lacks some libraries. If you install build-essential package, you will have ldd command available. This command ldd ./adb | grep not will show you what libraries are missing. Just install these libraries in i386 arch with apt. Like this: apt-get install libmissing:i386
    Beware, some buggy packages will try to delete 64bit version firs.






    share|improve this answer





















    • Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
      – Thomas Stuefe
      Apr 24 '14 at 12:30


















    7














    "No such file or directory" may appaear when you have your binary, but it lacks some libraries. If you install build-essential package, you will have ldd command available. This command ldd ./adb | grep not will show you what libraries are missing. Just install these libraries in i386 arch with apt. Like this: apt-get install libmissing:i386
    Beware, some buggy packages will try to delete 64bit version firs.






    share|improve this answer





















    • Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
      – Thomas Stuefe
      Apr 24 '14 at 12:30
















    7












    7








    7






    "No such file or directory" may appaear when you have your binary, but it lacks some libraries. If you install build-essential package, you will have ldd command available. This command ldd ./adb | grep not will show you what libraries are missing. Just install these libraries in i386 arch with apt. Like this: apt-get install libmissing:i386
    Beware, some buggy packages will try to delete 64bit version firs.






    share|improve this answer












    "No such file or directory" may appaear when you have your binary, but it lacks some libraries. If you install build-essential package, you will have ldd command available. This command ldd ./adb | grep not will show you what libraries are missing. Just install these libraries in i386 arch with apt. Like this: apt-get install libmissing:i386
    Beware, some buggy packages will try to delete 64bit version firs.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 24 '14 at 8:44









    Barafu AlbinoBarafu Albino

    4,90811832




    4,90811832












    • Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
      – Thomas Stuefe
      Apr 24 '14 at 12:30




















    • Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
      – Thomas Stuefe
      Apr 24 '14 at 12:30


















    Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
    – Thomas Stuefe
    Apr 24 '14 at 12:30






    Thank you, that would explain the weird error message. I was first confused why bash would give me this error (instead of some error coming more clearly from the child process which misses the libraries), but now I guess bash just sees exec(3) returning ENOENT and prints this out.
    – Thomas Stuefe
    Apr 24 '14 at 12:30













    4














    And if you want to use "adb" there is a package for it:



    sudo apt-get install android-tools-adb


    And about 32-bit libraries - only:



    sudo apt-add-architecture i386


    will be enough.






    share|improve this answer























    • Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
      – Thomas Stuefe
      Apr 24 '14 at 12:36










    • Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
      – aastefanov
      Apr 24 '14 at 12:44
















    4














    And if you want to use "adb" there is a package for it:



    sudo apt-get install android-tools-adb


    And about 32-bit libraries - only:



    sudo apt-add-architecture i386


    will be enough.






    share|improve this answer























    • Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
      – Thomas Stuefe
      Apr 24 '14 at 12:36










    • Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
      – aastefanov
      Apr 24 '14 at 12:44














    4












    4








    4






    And if you want to use "adb" there is a package for it:



    sudo apt-get install android-tools-adb


    And about 32-bit libraries - only:



    sudo apt-add-architecture i386


    will be enough.






    share|improve this answer














    And if you want to use "adb" there is a package for it:



    sudo apt-get install android-tools-adb


    And about 32-bit libraries - only:



    sudo apt-add-architecture i386


    will be enough.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 7 '15 at 5:06









    Anwar

    55.9k22145252




    55.9k22145252










    answered Apr 24 '14 at 12:29









    aastefanovaastefanov

    996815




    996815












    • Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
      – Thomas Stuefe
      Apr 24 '14 at 12:36










    • Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
      – aastefanov
      Apr 24 '14 at 12:44


















    • Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
      – Thomas Stuefe
      Apr 24 '14 at 12:36










    • Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
      – aastefanov
      Apr 24 '14 at 12:44
















    Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
    – Thomas Stuefe
    Apr 24 '14 at 12:36




    Thanks for the tip, but I wanted to use the android tools downloaded from google, not the ones in the Ubuntu repos. I am also not sure about the completeness of that package.
    – Thomas Stuefe
    Apr 24 '14 at 12:36












    Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
    – aastefanov
    Apr 24 '14 at 12:44




    Ubuntu repositories must have the new version. The package contains only adb. If you want fastboot - there is package for it too :)
    – aastefanov
    Apr 24 '14 at 12:44











    2














    Additionally to the excellent answer of Zanna and Avinash Raj I had to install gcc-multilib as well:



    sudo apt-get install gcc-multilib


    Possibly this is because I wanted to run an old gcc version on 64bit.






    share|improve this answer




























      2














      Additionally to the excellent answer of Zanna and Avinash Raj I had to install gcc-multilib as well:



      sudo apt-get install gcc-multilib


      Possibly this is because I wanted to run an old gcc version on 64bit.






      share|improve this answer


























        2












        2








        2






        Additionally to the excellent answer of Zanna and Avinash Raj I had to install gcc-multilib as well:



        sudo apt-get install gcc-multilib


        Possibly this is because I wanted to run an old gcc version on 64bit.






        share|improve this answer














        Additionally to the excellent answer of Zanna and Avinash Raj I had to install gcc-multilib as well:



        sudo apt-get install gcc-multilib


        Possibly this is because I wanted to run an old gcc version on 64bit.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Sep 4 '17 at 15:55









        Pierre.Vriens

        1,13761116




        1,13761116










        answered Sep 4 '17 at 13:52









        user2144067user2144067

        211




        211






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f454253%2fhow-to-run-32-bit-app-in-ubuntu-64-bit%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 reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?