User forums > Help

mingw32-gcc.exe: installation problem: cc1plus

(1/2) > >>

hill0093:
I downloaded codeblocks-1.0rc2_mingw and installed it.
The only non-standard thing I did was not include “Program Files” directory.
I opened a c program in codeblocks v1.0 .
I pressed Build > Compile current file.
It responded with
mingw32-gcc.exe: installation problem, cannot exec `cc1plus': No such file or directory.
C:\CodeBlocks\libexec\gcc\mingw32\3.4.4\cc1plus.exe  exists,
so I added it to Settings > Compiler > Directories with no avail.
I don’t know what to do.

raph:
RC2 is nearly two years old, please use a current nightly.

Haf:
Also, are you using Codeblocks and MingW under Windows Vista? If so, then please do a search in the forum, there are several threads related to the cc1plus issue in Windows Vista.

Short story: It should be sufficient to use the current Codeblocks and current stable MingW, add the directory of the cc1plus.exe to the Windows Path variable, have the compiler in a direct subfolder to the root folder of the hard drive (for instance c:\mingw\) and have the project files on the same hard drive as the compiler.
At least that's how it works for me with Vista.

There should also be a fixed unstable MingW version around that resolves the issues with Vista, but I haven't tried it as of yet.

TDragon:
20-40:

--- Quote from: 20-40 on July 16, 2007, 11:29:38 am ---BUT obviously MinGW should be installed into "mingw" directory, in your case C:\Codeblocks\mingw...

--- End quote ---
How, exactly, do you think this would solve any problems? Keep in mind that, as you mentioned further down in your post, the hardcoded directories are in "/mingw". On Unix systems this is a true absolute path -- or, if you like, relative to the filesystem root; on Windows it's relative to the root of the current drive. Therefore "/mingw" can never be resolved as "/Codeblocks/mingw", but only as "/mingw" (case insensitively, of course).

hill0093:
Windows environment variables are the key. I don't have Vista, but this post contains what I believe is everything one needs for command-line compilations to work. Note that there I am providing instructions for someone using my unofficial newer build of GCC; if you're using strictly packages from MinGW, you'll need to replace each instance of "4.2.0" with "3.4.5" or "3.4.2", depending on which version of the gcc-core and gcc-g++ packages you got. Also note that fewer environment variables are necessary when using MinGW/GCC from within Code::Blocks. As Haf said, searching the forum will turn up some useful information.

TDragon:

--- Quote from: 20-40 on July 16, 2007, 04:02:37 pm ---I've said it hundredths of times - this "mingw" folder could be in c:\codeblocks or in L:\PrOgRaMs or wherever one needs or wants.

--- End quote ---
Yes, and this time you said it I responded with a rebuttal. You're wrong. "/mingw" indicates a folder named "mingw" in the root of the drive, not "in c:\codeblocks or in L:\PrOgRaMs or wherever one needs or wants". Putting a folder named "mingw" somewhere other than the root of the drive means that "/mingw" will in no way correlate to it.

As a side note, the gcc.bat correspondence was not a recommendation to roland for an ongoing setup, but a test to help me understand how GCC is working (or not working) on Vista.

Navigation

[0] Message Index

[#] Next page