First API test, error 127.



  • Hello,

    We are building our first API in a Connectcore 6UL with Qt, but we keep getting error 127 when debugging.

    sudo apt-get install gcc g++ are installed.

    This is the output:

    16:44:13: Running steps for project untitled...
    16:44:13: Configuration unchanged, skipping qmake step.
    16:44:13: Starting: "/usr/bin/make"
    c -pipe -g -Wall -W -D_REENTRANT -fPIC -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5 -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtWidgets -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtGui -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtCore -I. -I. -I/opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o main.o main.cpp
    Makefile:545: recipe for target 'main.o' failed
    c -pipe -g -Wall -W -D_REENTRANT -fPIC -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5 -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtWidgets -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtGui -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtCore -I. -I. -I/opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o mainwindow.o mainwindow.cpp
    Makefile:549: recipe for target 'mainwindow.o' failed
    c -pipe -g -Wall -W -D_REENTRANT -fPIC -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5 -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtWidgets -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtGui -isystem /opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/include/qt5/QtCore -I. -I. -I/opt/dey/2.0-r5/sysroots/cortexa7hf-vfp-neon-dey-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o moc_mainwindow.o moc_mainwindow.cpp
    Makefile:552: recipe for target 'moc_mainwindow.o' failed
    o untitled main.o mainwindow.o moc_mainwindow.o -lQt5Widgets -L/home/builder/jenkins/workspace/dey-x11-release/projects/ccimx6ulsbc/tmp/work/ccimx6ulsbc-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib -lQt5Gui -lQt5Core -lGLESv2 -lpthread
    Makefile:214: recipe for target 'untitled' failed
    make: c: Command not found
    make: [main.o] Error 127 (ignored)
    make: c: Command not found
    make: [mainwindow.o] Error 127 (ignored)
    make: c: Command not found
    make: [moc_mainwindow.o] Error 127 (ignored)
    make: o: Command not found
    make: [untitled] Error 127 (ignored)
    16:44:13: The process "/usr/bin/make" exited normally.
    16:44:13: Connecting to device...
    16:44:14: The remote file system has 14 megabytes of free space, going ahead.
    16:44:14: Deploy step finished.
    16:44:14: No deployment action necessary. Skipping.
    16:44:14: Deploy step finished.
    16:44:14: Elapsed time: 00:01.

    Anyone has any ideas? Thanks in advance.


  • Lifetime Qt Champion

    Hi and welcome to devnet,

    Something looks wrong here you seem to have c being called rather that gcc

    Usually the default build tools are installed using the apt-get install build-essential.

    Looks like you are cross-compiling, are you sure the mkspec is setup correctly for your cross-compiler ?



  • @SGaist said in First API test, error 127.:

    Looks like you are cross-compiling, are you sure the mkspec is setup correctly for your cross-compiler ?

    Hi,

    We have also build-essential installed. Debugger, compiler, sysroot and qmake are those provided by the manufacturer in the toolchain. Cmake is the default /usr/bin/ one.

    Specifically, we have 2 compilers (arm-dey-linux-gnueabi-g++ and arm-dey-linux-gnueabi-gcc). Output is the same whichever we use.

    mkspec field in the kit tab is empty. No information about it was supplied by the manufacturer in the tutorial.

    The module is a i.mx6ul (has no GPU), if it is useful information.


  • Lifetime Qt Champion

    If possible a link to the tutorial would be nice.




  • Lifetime Qt Champion

    Did you create a custom mkspec for that board ?


Log in to reply
 

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