Skip to main content

Compiling in Qt Creator 2.0 problem - Error 127 [RESOLVED]

I had problems compiling simple programs in QT Creator, this happens when I try to compile a basic program too (Just build any code)

From Tools->Options->Qt4->"I check rebuild to see of qmake was working - but it gave the below error"

Code:
Running build steps for project chip...Creating gdb macros library...
Starting: /usr/bin/qmake-qt4 /home/ahmed/Qt/chip/chip.pro -spec
/usr/share/qt4/mkspecs/linux-g++ -r CONFIG+=debug_and_release
CONFIG+=debug Exited with code 0.Starting: /usr/bin/make debug -w make:
Entering directory `/home/ahmed/Qt/chip'/usr/bin/make -f Makefile.Debugmake[1]:
Entering directory `/home/ahmed/Qt/chip'g++ -c -pipe -g -Wall -W -D_REENTRANT
-DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL
-I/usr/include/qt4 -I/usr/X11R6/include -Idebug -I. -o debug/main.o main.cpp make[1]:
g++: Command not found
make[1]: *** [debug/main.o] Error 127make[1]:
Leaving directory `/home/ahmed/Qt/chip'make:
Leaving directory `/home/ahmed/Qt/chip'make:
*** [debug] Error 2Exited with code 2.
Error while building project ch
ip

To Solve this issue just install g++, I use Ubuntu 9.10
ahmed@ahmed-laptop:~$ sudo apt-get install g++

This solved the issue. :)

Posted via email from What I See

Comments

  1. im very impressed with your post because this post is very beneficial for me and provide a new knowledge to me
    Qt Creator 4.15.2 Crack

    ReplyDelete

Post a Comment

Popular posts from this blog

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Installing Zabbix Version 2.4 Offline (Zabbix Server without Internet).

There might be situations where you have a remote/zabbix server which does not have internet connectivity, due to security or other reasons. So we create a custom repo on the remote/zabbix server so that we can install zabbix using rpms Here is how we are planning to do this. Download all the dependency rpms on a machine which has internet connection, using yum-downloadonly or repotrack . Transfer all the rpms to the remote server. Create a repo on the remote server. Update yum configuration. Install. NOTE: This method can be used to install any application, but here we have used zabbix as we had this requirement for a zabbix server. Download dependent rpms . On a machine which has internet connection install the package below. And download all the rpms . Make sure the system are similar (not required to be identical - At-least the OS should be of same version) mkdir /zabbix_rpms yum install yum-downloadonly Downloading all the rpms to location /zabbix_rpms/ ,

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa