HELP!

[Robert Lipe]

Picking good subject lines is more likely to get you a good answer.

> Well , the problem is EGCS. I installed it ( set paths,env.vars,and
> unpacked) ...and...the problem is : 

Similarly: 
   * list versions (there are several of EGCS) 
   * the target OS (we can deduce it's some form of windows mutant) 
   * if it's a binary kit where you got it.   Some of the binary kits are
     best supported by the group that assembled them.
   * If you built it yourself, the configure triplets used, problems during
     the build and so on.

>  1/ the names of  cpp.exe is c++.exe, gxx is g++ here and cxxfilt is
> c++filt and libs have pluses in their names and directories etc.
> However,system makes these names scrambled eg. g++ changes to G__~1.exe and
> so on. The funny thing is that gcc.exe of EGCS needs cpp.exe ,not
> c++.exe,because it writes that it can't find cpp.exe if the name is the
> original version (c++).
>
> I changed what i could ( everything,my version of names was just djgpp
> version) and wanted to compile simplest C proggy ( main(){}) with : gcc
> proggy.c -o proggy.exe and the output was:

`cpp' is a c preprocessor. `c++' is a compiler for the language named
c++.  Renaming one to the other is a bad idea becuase it won't do
anything productive.

Different OSes have different naming rules.  Different OSes will grok
things differently such as the addition of `.exe', renaming g++ to gxx,
etc.  If you have a binary kit and you think things in it are named
'funny', you should check the instructions with that kit.


Disclaimer:  I don't do windows so don't ask me. :-)