X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: Build problems - unistd.h Date: Tue, 29 May 2007 20:00:12 -0500 Lines: 29 Message-ID: References: <465CCB43 DOT 7040505 AT cox DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.0 In-Reply-To: <465CCB43.7040505@cox.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Greg Chicares wrote: > On 2007-05-30 00:12Z, Scott Peterson wrote: >> Here's the content of the intermediate file dbus-binding-tool-glib.i: > > [major snip] > > On 2007-05-29 02:07Z, you had written: >> In file included from /usr/include/unistd.h:4, >> from dbus-binding-tool-glib.c:39: >> /usr/include/sys/unistd.h:108: error: parse error before numeric constant > > Look at line 108 of that file. In my copy, it's a prototype > for _pipe() . Now look for _pipe() in the preprocessed output: > >> int __attribute__((__cdecl__)) _pipe (int __fildes[2], 4096, _O_BINARY); > > Maybe that's the "parse error before numeric constant"? > > What does line 108 in your /usr/include/sys/unistd.h say, > exactly? Assuming it's not corrupted, the real question is > how it got turned into the preprocessed line above. ...to hazard a guess, I suspect some .h has '#define pipe(a) _pipe(a, 4096, _O_BINARY)'. -- Matthew "A mouse is a device used to point at the xterm you want to type in." --Kim Alm, A.S.R. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/