Mail Archives: djgpp/2001/01/04/09:30:28
On Thu, 4 Jan 2001, Michael Noel Jones wrote:
> I have been having a similar problem on WinNT; Using gcc2.95.2, I was
> getting this same "installation problem: cannot exec 'cpp'".
Please post the output of compilation with -v switch added to the
compiler command line here, like the user who started this thread did.
As you saw, given that output, such problems are usually solved in no
time.
> The FAQ
> says that with gcc2.8.x and older that cpp has been moved. It claims
> that the problems.txt file gives instructions on what to change in
> DJGPP.env, but as noted, there is no mention of this problem.
Those instructions were removed from latest versions of GCC because they
are no longer needed. You simply need to install GCC as the README says.
> The FAQ also claims that the "COMPILER_PATH" environment variable might
> need to be set. But fails to suggest what it might need to be set to.
COMPILER_PATH is documented in the GCC docs. The FAQ is not a
replacement for every piece of documentation users should read.
> I eventually added D:\DJGPP\lib\gcc-lib\djgpp\2.952 to my PATH (this is
> where cpp, cpp1 etc reside).
That's a very bad idea. You might have created new exciting problems for
you.
I suggest to remove this directory from PATH and solve the original
problems instead. Given the output printed by the compiler under -v, I
assure you that the problem will be solved quickly and efficiently.
> Now I get the error:
> C:\Program Files\DevStudio\MyProjects\VCServices\foo2>make
> d:/djgpp/bin/gpp.exe -c -o main.o main.cpp
> -IC:/[own_include_path]/include -ID:\DJGPP\include\sys
> cpp.exe: ../include/sys/version.h: No such file or directory (ENOENT)
> make.exe: *** [main.o] Error 1
Again, add -v to the compiler command line and post here what it prints
(looking into that output might give you a clue, so I suggest to read
what it prints before you post).
> Obviously cpp is looking in the wrong place for the include files. Where
> is the information on sorting this problem out? Why is it not in the
> FAQ?
The FAQ only lists problems which are _frequently_ asked about.
> Why does the FAQ refer to a document that doesn't even mention the
> problem?
Because the FAQ attempts to be correct for several different versions of
GCC, and is not always updated to track all the latest developments. In
other words, I simply don't have enough resources to do more than what
I already do, sorry. If someone is willing to take over the FAQ
maintenance, I will gladly relinquish my responsibilities.
> P.S. One reply to this claimed that Andreas' DJGPP entry in PATH should
> be moved before the ESX entry....the PATH variable was listed and
> plainly contains no reference to ESX. (Unless it's in C:\WINDOWSor
> C:\WINDOWS\COMMAND)
It was EMX, not ESX.
It's true that the PATH command as posted didn't say anything about EMX.
And yet it is crystal clear from reading the output of "gcc -v" that it
was an EMX-compiled gcc. So the actual PATH used when the compilation was
done did somehow include the EMX directory. Typing "PATH [Enter]" in the
same DOS box where you compile might reveal what PATH really is.
(Sometimes, directories are added to PATH by all kinds of scripts and
Registry settings that are run when the DOS box is opened.)
- Raw text -