X-Spam-Check-By: sourceware.org Date: Thu, 31 May 2007 10:31:07 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Scott Peterson cc: cygwin AT cygwin DOT com Subject: Re: Build problems - unistd.h In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Thu, 31 May 2007, Scott Peterson wrote: > 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! You could try simply inserting '#undef pipe' before '#include '. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- 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/