Date: Tue, 24 Mar 1998 13:08:02 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Eugene Ageenko <ageson AT cs DOT joensuu DOT fi>
cc: bug-gcc AT prep DOT ai DOT mit DOT edu, djgpp AT delorie DOT com
Subject: Re: Problems with GCC 2.8.0
In-Reply-To: <35167571.33220523@cs.joensuu.fi>
Message-ID: <Pine.SUN.3.91.980324130744.21946D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 23 Mar 1998, Eugene Ageenko wrote:

> First, is that GCC does not want to compile the program having more
> than one module, let say test.c and module.c following way:
> 
> >gcc test.c module.c -o test

Please add -v to this command line and post everything it prints.
Also, please explain what do you mean by ``does not compile''.  Does
it print an error message and quit?  Does it crash?  Doesn't it
generate the executable file `test.exe'?  What exactly is the problem?

> >gcc -c TEST.C
> gcc.exe: installation problem, cannot exec `cc1plus': No such file
> or directory (ENOENT)

That's not a bug, that's a feature.  A file with a .C extension is a
C++ file, so GCC is looking for a C++ compiler (cc1plus.exe) which you
haven't installed.  This is explained in section 8.4 of the DJGPP FAQ
list (v2/faq210b.zip from the same place you get DJGPP).

> I understand that gcc is not caseinsensitive and that it treats .C
> files as the C++ files, but what about cc1plus then? Where it is
> from?

cc1plus is in gpp280b.zip distribution.  But I think it's a bad idea
to compile a C source with the C++ compiler.  C++ is a different
language, so you most probably will have a lot of weird warning and
error messages if you do that.

> Unfortunately my shell type the names in CAPITAL letters that causes
> the problem.

You *must* find a way to work around this shell ``feature''.  Maybe if
you explain how the capital letters get to the GCC command line, we
could help you find a solution.  (You do seem to be able to say "gcc -o" 
in lower case.)