Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <99B82AA9708ED0119B55006097125A00363E74@ifk63.mach.uni-karlsruhe.de>
From: Heribert Dahms <heribert_dahms AT icon-gmbh DOT de>
To: "'Jay Krell'" <jay DOT krell AT cornell DOT edu>,
        Sarab Duhra
	 <Sarab_D1 AT verifone DOT com>, cygwin AT sourceware DOT cygnus DOT com
Subject: RE: Error in stddef.h line 1
Date: Fri, 28 Apr 2000 23:04:45 +0200
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: multipart/mixed;
	boundary="---- =_NextPart_000_01BFB166.25E68C70"

------ =_NextPart_000_01BFB166.25E68C70
Content-Type: text/plain

Please refer to Larry's answer in the attachment!

Bye, Heribert (heribert_dahms AT icon-gmbh DOT de)

> -----Original Message-----
> From:	Jay Krell [SMTP:jay DOT krell AT cornell DOT edu]
> Sent:	Friday, April 28, 2000 15:01
> To:	Sarab Duhra; cygwin AT sourceware DOT cygnus DOT com
> Subject:	Re: Error in stddef.h line 1
> 
> >/usr/lib/gcc-lib/i686-cygwin/2.95.2/include/stddef.h:1: Invalid token
> in
> >expression
> 
> What does your stddef.h look like?
> Mine starts out:
> #if (!defined(_STDDEF_H) && !defined(_STDDEF_H_) &&
> !defined(_ANSI_STDDEF_H)
> \
>      && !defined(__STDDEF_H__)) \
>     || defined(__need_wchar_t) || defined(__need_size_t) \
>     || defined(__need_ptrdiff_t) || defined(__need_NULL) \
>     || defined(__need_wint_t)
> 
>  - Jay
> 
> [Heribert]  [snip]
>  
>  

------ =_NextPart_000_01BFB166.25E68C70
Content-Type: message/rfc822

Message-ID: <4 DOT 3 DOT 1 DOT 2 DOT 20000428103611 DOT 00bb5510 AT pop DOT ma DOT ultranet DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
To: Olivier Jacquemin <Olivier DOT Jacquemin AT DialogSystems DOT be>, 
	"cygwin AT sourceware DOT cygnus DOT com" <cygwin AT hotpop DOT com>
Subject: Re: Backslash (stray) not treated correctly by gcc
Date: Fri, 28 Apr 2000 16:44:52 +0200
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain

At 04:24 AM 4/28/00, Olivier Jacquemin wrote:
>Hello,
>
>After successful installation of cygwin 1.1.0, I tried to compile a
very
>simple program beginning with
>
>#include <stdio.h>
>
>but gcc complains about the following structure from the sys/reent.h
file
>included by stdio.h:
>
>#define _REENT_INIT(var) \
>   { 0, &var.__sf[0], &var.__sf[1], &var.__sf[2], 0, "", 0, "C", \
>     0, NULL, NULL, 0, NULL, NULL, 0, NULL, { {1, NULL, "", \
>     { 0,0,0,0,0,0,0,0}, 0 } } }
>
>The first error message is
>
>/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../i686-pc-cygwin/inclu
de/sy
>s/reent.h:212: parse error before `{'
>
>which refers to the second line of the above structure.  Obviously the
>backslash character is not treated correctly.  I get a similar error
>somewhere in the stdio.h file itself, again backslash not recognized as
it
>should:
>
>#define __sputc(c, p) \
>         (--(p)->_w < 0 ? \
>
>-->
>/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../i686-pc-cygwin/inclu
de/st
>dio.h:269: parse error before `--'
>
>Any fix for this ?
>
>Thanks much,
>
>         _Olivier_



Parse errors in system include files are most often the result of
text/binary
mode incompatibilities.  If you check this file with a binary editor,
you 
will most likely see \r\n line endings.  My guess is that the mount
point 
that you have for / is binary (default in the latest net release).  If
you
want to interpret files in text mode, you should mount text mode.  If
you want to keep binary mounts which will open all files (not otherwise 
specified) as binary, you need to remove the \r from files like stdio.h.
Its your choice and once you make the decision and route out all the 
incompatible files, you'll find things are pretty smooth sailing.  Of 
course, as with any half-baked idea like different formats for files in 
different "modes", you'll still find cases where you're "damed if you do
and damned if you don't."

Good luck!



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX
                                        (508) 560-1285 - cell phone



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


------ =_NextPart_000_01BFB166.25E68C70
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
------ =_NextPart_000_01BFB166.25E68C70--