This is the mail archive of the
mailing list for the Cygwin project.
Re: Bad CPP.EXE on GCC 2.95.2 ??
- To: <cygwin at sourceware dot cygnus dot com>
- Subject: Re: Bad CPP.EXE on GCC 2.95.2 ??
- From: Daniel Bermudez <danielbermudez at earthlink dot net>
- Date: Mon, 19 Jun 2000 07:14:51 -0500
You're right! The file was littered with CRLFs coming from the backup!
on 6/18/00 8:09 PM, Chris Faylor at firstname.lastname@example.org wrote:
> On Sun, Jun 18, 2000 at 08:01:41PM -0500, Daniel G. Bermudez wrote:
>> Just recently reinstalled Win98 on my system, which is sort of a ritual
>> or sorts, and while running Cygwin's 'gcc' compiler after reinstalling
>> (with gcc's version 2.95.2-1 ) I did find that 'cpp' return this ugly
>> message on code that has compiled before without problems!
> You probably have CRLF line endings!
> Either eliminate them or mount the directory in question as "text-mode",
> Also make sure that you are running the cygwin 1.1.2 DLL.
> For information on the mount command and text mode in general, check out
> the documentation at the project web site:
>> BASH.EXE-2.04$ gcc -o runthis adamklist.c
>> adamklist.c:1: `#include' expects "FILENAME" or <FILENAME>
>> ...omitting the header on the file and the content below, these are the
>> offending lines;
>> #include <stdlib.h>
>> #include <stdio.h>
>> #include <math.h>
>> #include <string.h>
>> #include <sys/types.h>
>> #include <sys/param.h>
>> #include <unistd.h>
>> #include <mingw32/dir.h>
>> /*#include <regexpr.h>*/
>> #define TRUE 1
>> I'd tried reinstalling gcc using the 'setup gcc' command, but exactly
>> the same thing! What are your suggestions??
Want to unsubscribe from this list?
Send a message to email@example.com