X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 31 May 2007 00:03:05 -0400 From: "Scott Peterson" To: cygwin@cygwin.com Subject: Re: Build problems - unistd.h In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Sorry about the large email: didn't realize how big it was when I cut and pasted. Line 108 is indeed: int _EXFUN(pipe, (int __fildes[2] )); I've greped around for "define pipe" and the only results I could find are /usr/include/glib-1.2/glib.h and /usr/include/glib-2.0/glib/gwin32.h. Both files define precisely the method you mention: #define pipe(phandles) _pipe (phandles, 4096, _O_BINARY) Here's the kicker: I commented out both instances of that #define and the build still fails with the same error. Is there anyway I can find out precisely where the preprocessor is getting that method? C really isn't my thing so when I have problems like this with prerequisite packages, I'm really at a loss. Thanks everyone for lending me a hand with this! > 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)'. > -- Scott. -- 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/