Date:	Sun, 22 Feb 1998 13:40:07 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Dave Maranhao <davem2 AT ma DOT ultranet DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: What's going on?
In-Reply-To:	<34ef6956.3878249@news.ma.ultranet.com>
Message-ID:	<Pine.SUN.3.91.980222133942.19567V-100000@is>
MIME-Version:	1.0

On Sun, 22 Feb 1998, Dave Maranhao wrote:

> C:\DJGPP>gcc hello.c -v
>
> Reading specs from c:/djgpp/lib\specs
> gcc version 2.7.2.1
> c:\djgpp/bin\cpp.exe _lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=7
> -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=1 -D__unix__
> -D__i386__ -D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D_DJGPP_MINOR__=1
> -D__unix -D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=1
> hello.c c:/djgpp/tmp\ccbaaaaa
> GNU CPP version 2.7.2.1 (80386, BSD syntax)
> #include "..." search starts here:
> #include <...> search starts here:
> c:/djgpp/bin\cc1.exe c:/djgpp/tmp\ccbaaaaa -quiet -dumpbase hello.c
> -version -o c:/djgpp\tmp\cccaaaaa

That's the wierdest output I have ever seen.  GCC should have invoked
the assembler (as.exe), the linker (ld.exe) and stubify.exe after
cc1.exe, but somehow it didn't!

Also, the search paths of cpp.exe are empty(??) although the -D
switches passed by GCC indicate that the DJGPP *is* set correctly.
What's going on here??!!??

Are you sure this is all that was printed?  If not, please post the
*exact* and *complete* output of GCC, it is vital to help you solve
your problem(s).

Also, please post a complete description of your system setup,
including CONFIG.SYS, AUTOEXEC.BAT and the output of the command "set"
when typed from the DOS prompt.  If you are using some non-standard
software, like a shell other than COMMAND.COM, please tell so as well.

- Raw text -