www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/09/16/08:42:01

Date: Tue, 16 Sep 1997 15:41:32 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: *** Brett *** <bporter AT rabble DOT uow DOT edu DOT au>
cc: DJGPP <djgpp AT delorie DOT com>
Subject: Re: Command-line compiling: cpp.exe not found
In-Reply-To: <199709160156.LAA23892@rabble.uow.edu.au>
Message-ID: <Pine.SUN.3.91.970916154100.25597G-100000@is>
MIME-Version: 1.0

On Tue, 16 Sep 1997, *** Brett *** wrote:

> I cannot compile from the command line anymore with instructions like gcc -c
> file.cc -o file.o OR gcc file.cc. It always comes up with cpp.exe: : not
> found (ENOENT) -- or something to that effect.

Please make a point of reporting the error messages exactly, not
``something to that effect''.  It is very hard to remote-debug your
problems when you don't even tell what's printed on your screen.

Please add -v to the gcc command line and post everything that's
printed.  You might want to redirect the messages to a file.  The
easiest way to do that is by running gcc via `redir' utility:

	redir -o gcc.log -eo gcc -v -c file.cc

The messages get redirected to the file gcc.log, which you should
post.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019