Compile error: "g++: error trying to exec 'cc1plus': execvp: No such file or directory"

All we need is an easy explanation of the problem, so here it is.

When I compile C/C++ program with popen in php… I got this error:

g++: error trying to exec 'cc1plus': execvp: No such file or directory

but if I run php code in shell.. it works fine..

in Arch Linux..

PHP Code:

    function rfile($fp) {
       while (!feof($fp)) {
           $out.= fgets($fp, 1024000);
       return $out;
    $p = popen('g++ -Wall -g -o aplusb 2>&1', 'r');
    $result = rfile($p);
    echo $result;


How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

You need to install gcc-c++ package.

yum install gcc-c++

Method 2

I don’t know why but i just renamed my source file COLARR.C to colarr.c and the error vanished!
probably you need this

sudo apt-get install g++

Method 3

This problem can happen if different versions of g++ and gcc are installed.

   g++ --version
   gcc --version

If these don’t give the result, you probably have multiple versions of gcc installed. You can check by using:

    dpkg -l | grep gcc | awk '{print $2}'

Usually, /usr/bin/gcc will be sym-linked to /etc/alternatives/gcc which is again sym-linked to say /usr/bin/gcc-4.6 or /usr/bin/gcc-4.8 (In case you have gcc-4.6, gcc-4.8 installed.)

By changing this link you can make gcc and g++ run in the same version and this may resolve your issue!

Method 4

Each compiler has its own libexec/ directory. Normally libexec directory contains small helper programs called by other programs. In this case, gcc is looking for its own ‘cc1’ compiler. Your machine may contains different versions of gcc, and each version should have its own ‘cc1’. Normally these compilers are located on:


Similar path for g++. Above error means, that the current gcc version used is not able to find its own ‘cc1’ compiler. This normally points to a PATH issue.

Method 5

For apk, easiest way is:

apk add build-base

Method 6

I had the same issue when forking with ‘python’; the main reason is that the search path is relative, if you don’t call g++ as /usr/bin/g++, it will not be able to work out the canonical paths to call cc1plus.

Method 7

Install g++
on openSuSE run

zypper in gcc-c++

Method 8

Something went wrong with your GCC installation. Try reinstalling the it like this:

sudo apt-get install --reinstall g++-5

In Ubuntu the g++ is a dependency package that installs the default version of g++ for your OS version. So simply removing and installing the package again won’t work, cause it will install the default version. That’s why you need to reinstall.

Note: You can replace the g++-5 with your desired g++ version. To find your current g++ version run this:

g++ --version

Method 9

You may have this issue as well if you have environment variable GCC_ROOT pointing to a wrong location. Probably simplest fix could be (on *nix like system):

unset GCC_ROOT

in more complicated cases you may need to repoint it to proper location

Method 10

I had the same issue with gcc “gnat1” and it was due to the path being wrong. Gnat1 was on version 4.6 but I was executing version 4.8.1, which I had installed. As a temporary solution, I copied gnat1 from 4.6 and pasted under the 4.8.1 folder.

The path to gcc on my computer is /usr/lib/gcc/i686-linux-gnu/

You can find the path by using the find command:

find /usr -name "gnat1"

In your case you would look for cc1plus:

find /usr -name "cc1plus"

Of course, this is a quick solution and a more solid answer would be fixing the broken path.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply