[Beginner] Parsing errors compiling headers

[Ed Bradford/Raleigh/IBM]

I have most often seen the "parse error" on files whith have the CRLF
problem. Apparently, gcc can adequately parse
both LF and CRLF except when a macro spans lines. At least that is the
experience I have had, I could be wrong about precisely
when it can handle both and when it can't. Regrettably, I solve the problem
by copying the header files to the local
directory and changing the compile line to look in dot ("-I.") during
compilation. I wish there were a more general solution. The
problem is some files that end up in /usr/include have LF and some have
CRLF. The bad thing about all this is that if you
use diff to try to detect what is wrong, it shows every single line as
different. That is my general indication that it is the CRLF issue arising.

Ed


Your Windows 2000 Arborist
T/L 589-4410; Outside: 1-919-993-4410
egb@us.ibm.com


Paulius Bulotas <Paulius@CSDL.LT>@sources.redhat.com on 10/25/2000 02:19:31
PM

Sent by:  cygwin-owner@sources.redhat.com


To:   "CYGWIN (E-mail)" <cygwin@sourceware.cygnus.com>
cc:
Subject:  [Beginner] Parsing errors compiling headers



Hello,

just starting to remember hot to use old good C and tried to compile one
program (own), using Microsofts supplied header files.
But i just get a lot of warnings as this:
//d/PROGRAMs/MSDASDK/INC/sqltypes.h:137: parse error before `SQLHWND'
and so on and so on.
everything was done from cmd.exe (not bash and cygwin),
gcc cmdline: gcc -DWIN32 -I//d/PROGRAMS/MSDASDK/INC
-L//d/PROGRAMS/MSDASDK/LIB/X86 -lodbc32 -c odbc.c -o odbc -mno-cygwin

I think it's not first such case/question, but somebody help! please ;)
TIA

Regards,
Paulius

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com