Martin Wolters wrote: > On Wednesday 05 March 2003 17:19, Max Bowsher wrote: >> Martin Wolters wrote: >>> On Wednesday 05 March 2003 16:18, [EMAIL PROTECTED] wrote: >>>> OK. And that file contains only C code? >>> >>> That's a good question. I thought so and I still think so. However, >>> I just tried "g++ myCFile.c" and it compiles like a charm!! >>> >>> Well, maybe I can find the code that breaks the gcc-build. And if it >>> turns out to be a valid c-construct I'll send the requested >>> informationen. But for now I at least have a "workaround". >> >> foo.C means C++. Could your file extension be uppercase accidentally? > > Now that is interesting and it actually is the cause of all troubles. > My file is really called "MYCFILE.C". Renaming it (mycfile.c) and > then using gcc mycfile.c works perfectly. > > I didn't now the upper-case C rule. Is that gcc-specific?
I found this by googling on "C cpp c++ cxx cc": Compiler possible endings GNU compiler g++ C cc cpp cxx c++ Watcom C++ -- cc cpp cxx c++ Borland C++ -- cc cpp cxx c++ SGI compiler CC C cc cpp cxx c++ DEC compiler cxx C cc cpp cxx -- Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
