Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Importance:	Normal
Subject:	Re: [Beginner] Parsing errors compiling headers
To:	cygwin AT sourceware DOT cygnus DOT com
X-Mailer:	Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID:	<OFE3D7DF08.3636BB49-ON85256983.0066BD03@raleigh.ibm.com>
From:	"Ed Bradford/Raleigh/IBM" <egb AT us DOT ibm DOT com>
Date:	Wed, 25 Oct 2000 14:45:29 -0400
X-MIMETrack:	Serialize by Router on D04NMS90/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at
	10/25/2000 02:45:31 PM
MIME-Version:	1.0

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 AT us DOT ibm DOT com


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

Sent by:  cygwin-owner AT sources DOT redhat DOT com


To:   "CYGWIN (E-mail)" <cygwin AT sourceware DOT cygnus DOT 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 AT sourceware DOT cygnus DOT com




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -