Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. error while deploying to remote device
Forum Update on Monday, May 27th 2025

error while deploying to remote device

Scheduled Pinned Locked Moved Unsolved General and Desktop
6 Posts 2 Posters 651 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mijaz
    wrote on 11 Nov 2019, 03:57 last edited by Mijaz 11 Nov 2019, 04:07
    #1
    bash: /home/analog/Desktop/myqt512: cannot execute binary file: Exec format error
    bash: /home/analog/Desktop/myqt512: Success
    
    Application finished with exit code 126.
    

    Although I am using same compiler for qt4.8.7 version and that is working fine

    J 1 Reply Last reply 11 Nov 2019, 05:27
    0
    • M Mijaz
      11 Nov 2019, 03:57
      bash: /home/analog/Desktop/myqt512: cannot execute binary file: Exec format error
      bash: /home/analog/Desktop/myqt512: Success
      
      Application finished with exit code 126.
      

      Although I am using same compiler for qt4.8.7 version and that is working fine

      J Offline
      J Offline
      jsulm
      Lifetime Qt Champion
      wrote on 11 Nov 2019, 05:27 last edited by
      #2

      @Mijaz You did not cross compile for target device, right?
      What is your device?
      Also, when asking questions please provide enough information (here you did not even say what device that is).

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      M 1 Reply Last reply 11 Nov 2019, 10:24
      3
      • J jsulm
        11 Nov 2019, 05:27

        @Mijaz You did not cross compile for target device, right?
        What is your device?
        Also, when asking questions please provide enough information (here you did not even say what device that is).

        M Offline
        M Offline
        Mijaz
        wrote on 11 Nov 2019, 10:24 last edited by
        #3

        @jsulm
        I am using SDR ad9361 board,
        my device architecture is : armv7l

        while configuration I have not selected any device because
        mkspec /device : there is no device source available for my board.

        J 1 Reply Last reply 11 Nov 2019, 13:18
        0
        • M Mijaz
          11 Nov 2019, 10:24

          @jsulm
          I am using SDR ad9361 board,
          my device architecture is : armv7l

          while configuration I have not selected any device because
          mkspec /device : there is no device source available for my board.

          J Offline
          J Offline
          jsulm
          Lifetime Qt Champion
          wrote on 11 Nov 2019, 13:18 last edited by
          #4

          @Mijaz Well, you can't execute x86 binaries on non x86 platforms.
          You can check what you executable is doing:

          file /home/analog/Desktop/myqt512
          

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          M 1 Reply Last reply 12 Nov 2019, 05:02
          1
          • J jsulm
            11 Nov 2019, 13:18

            @Mijaz Well, you can't execute x86 binaries on non x86 platforms.
            You can check what you executable is doing:

            file /home/analog/Desktop/myqt512
            
            M Offline
            M Offline
            Mijaz
            wrote on 12 Nov 2019, 05:02 last edited by Mijaz 11 Dec 2019, 05:03
            #5

            @jsulm

            Yes exactly, you are right. As my application myqt5.12_test: ELF 64-bit LSB  shared object, x84-64, version 1 (SYSV)
            this is not working.
            
            myqt4.8.7_test: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV)
            this is working fine. 
            

            the configuration process auto select the x84-64 architecture with ELF 64-bit LSB. I had built the qt5.12.5 without specifying the device target because when I try to specify my target then it gets the error .

            > collect2: error: ld returned 1 exit status
            > Makefile:68: recipe for target 'verifyspec' failed
            > make: *** [verifyspec] Error 1
            Note: Also available for Linux: linux-clang linux-icc
            
            

            Now I am trying newly build all these files for qt 5.13.0 with compiler 4.9

            ijaz@ijaz-HP-ProDesk-400-G4-MT:~/qt_5_13_configure$  ~/qt_5_13_sources/qt-everywhere-src-5.13.0/configure -release -device linux-arm-generic-g++ -device-option CROSS_COMPILE=~/qt_5_13_root/gcc-linaro-arm-linux-gnueabihf-4.9-2014.07_linux/bin/arm-linux-gnueabihf- -opensource -confirm-license -skip qtwayland -skip qtlocation -skip qtscript -make libs -prefix /usr/local/qt_5_13 -extprefix ~/qt_5_13_root/analog -hostprefix ~/qt_5_13_root/qt5_13 -no-use-gold-linker -v -no-gbm
            
            

            But this also returns above error

             Makefile:68: recipe for target 'verifyspec' failed
            

            How I can Build for my device "arm" ?

            J 1 Reply Last reply 12 Nov 2019, 05:17
            0
            • M Mijaz
              12 Nov 2019, 05:02

              @jsulm

              Yes exactly, you are right. As my application myqt5.12_test: ELF 64-bit LSB  shared object, x84-64, version 1 (SYSV)
              this is not working.
              
              myqt4.8.7_test: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV)
              this is working fine. 
              

              the configuration process auto select the x84-64 architecture with ELF 64-bit LSB. I had built the qt5.12.5 without specifying the device target because when I try to specify my target then it gets the error .

              > collect2: error: ld returned 1 exit status
              > Makefile:68: recipe for target 'verifyspec' failed
              > make: *** [verifyspec] Error 1
              Note: Also available for Linux: linux-clang linux-icc
              
              

              Now I am trying newly build all these files for qt 5.13.0 with compiler 4.9

              ijaz@ijaz-HP-ProDesk-400-G4-MT:~/qt_5_13_configure$  ~/qt_5_13_sources/qt-everywhere-src-5.13.0/configure -release -device linux-arm-generic-g++ -device-option CROSS_COMPILE=~/qt_5_13_root/gcc-linaro-arm-linux-gnueabihf-4.9-2014.07_linux/bin/arm-linux-gnueabihf- -opensource -confirm-license -skip qtwayland -skip qtlocation -skip qtscript -make libs -prefix /usr/local/qt_5_13 -extprefix ~/qt_5_13_root/analog -hostprefix ~/qt_5_13_root/qt5_13 -no-use-gold-linker -v -no-gbm
              
              

              But this also returns above error

               Makefile:68: recipe for target 'verifyspec' failed
              

              How I can Build for my device "arm" ?

              J Offline
              J Offline
              jsulm
              Lifetime Qt Champion
              wrote on 12 Nov 2019, 05:17 last edited by
              #6

              @Mijaz said in error while deploying to remote device:

              I have built the qt5.12.5 without specifying the device target

              That will not work. You have to cross compile Qt.
              Please take a look at what @SGaist wrote in one of your other threads.

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0

              1/6

              11 Nov 2019, 03:57

              • Login

              • Login or register to search.
              1 out of 6
              • First post
                1/6
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups
              • Search
              • Get Qt Extensions
              • Unsolved