arm-linux-gnueabihf-g++: Command not found

  • I was followed these are steps

    I used:

    1. wget

    2. tar -xzf qt-everywhere-opensource-src-4.8.6.tar.gz
      Rename the folder to something more convenient:

    3. mv qt-everywhere-opensource-src-4.8.7 qt-4.8.7-beagle

    4. Go to the folder:
      cd qt-4.8.7-beagle

    5. Copy the folder:

    cp -r mkspecs/linux-arm-gnueabi-g++/ mkspecs/linux-arm-gnueabihf-g++/

    1. Edit the qmake.conf file:

    nano mkspecs/linux-arm-gnueabihf-g++/qmake.conf

    Change all references of “arm-linux-gnueabi” to “arm-linux-gnueabihf” (add the “hf”)
    For instance, arm-linux-gnueabi-gcc becomes arm-linux-gnueabihf-gcc.
    Save the file and exit.

    1. In the root of the new qt directory, create a config script file:

    nano config

    1. Add the line:

    ./configure -v -opensource -confirm-license -xplatform linux-arm-gnueabihf-g++ -embedded arm -little-endian -host-little-endian -prefix /usr/local/qt4.8.6-armhf
    Save and exit.

    1. Make it executable:

    chmod 700 config

    1. Configure, build, and install:

    sudo make install

    I was got this is an error :

    make[1]: arm-linux-gnueabihf-g++: Command not found
    make[1]: *** [.obj/release-shared-emb-arm/qabstractanimation.o] Error 127
    make[1]: Leaving directory `/home/essen-s1/qt-4.8.7-beagle/src/corelib'
    make: *** [sub-corelib-make_default-ordered] Error 2

  • @sekhar said in arm-linux-gnueabihf-g++: Command not found:

    make[1]: arm-linux-gnueabihf-g++: Command not found

    it looks like you're missing the toolchain (i.e. cross-compiler) installed in your host machine

  • I installed " gcc-arm-linux-gnueabihf " toolchain.
    but it does't work.

  • @sekhar said in arm-linux-gnueabihf-g++: Command not found:

    but it does't work.

    It doesn't look like a good troubleshooting report...
    What does not work? didn't it brew coffee for instance?
    Please provide any error output if you mind.


Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.