X-Spam-Check-By: sourceware.org Date: Tue, 24 Jan 2006 17:27:01 -0500 (EST) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: pobox AT verysmall DOT org cc: cygwin AT cygwin DOT com Subject: Re: Errors compiling cdrtools under cygwin 1.5.19 In-Reply-To: <43D69F82.8050209@verysmall.org> Message-ID: References: <012420061825 DOT 2204 DOT 43D671090006A0AD0000089C22092299270A050E040D0C079D0A AT comcast DOT net> <20060124183552 DOT GA2889 AT trixie DOT casa DOT cgf DOT cx> <43D69F82 DOT 8050209 AT verysmall DOT org> 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-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 Tue, 24 Jan 2006, pobox wrote: > > This falls into the same category as my previous discussion about > > _POSIX_SOURCE. If a program builds without problem on linux, the goal > > is for it to build without problem on cygwin. It seems like the > > unconditional addition of getline to the headers moves us a step back > > from that goal. > > Is this also valid for Apache 1.3.34? > > I think it compiles without problem on Linux, but does not compile on > cygwin since getline() was implemented last month. This is a simple name clash. Linux also defines getline (also with an incompatible prototype). htpasswd.c defines its own getline(), and it should have the same problem on any system with getline(). You have to check why it compiles (in particular, check the pre-processed form of htpasswd.c using "gcc -E"). > I do not want to heat the discussion, but getline() in cygwin played > very hard against me. > > I used cygwin happily for very long time to compile > apache/php/postgresql and enjoy symlinks, and now I am cut-off from one > day to the next. The apache folks do not seem to care. The bug I > submitted is still without reply - > > http://issues.apache.org/bugzilla/show_bug.cgi?id=38364 That's because the Apache community has apparently been ignoring this issue since 2002: (which, BTW, contains a patch that you can apply to fix this issue). > Apache 2.x/php 5.x do not want to play on cygwin so far. I seem to recall either Brian or Max reporting that they were able to compile PHP 5.x with the Cygwin Apache2 package. Search the cygwin-apps archives. > So I am three days in the dark and testing like hell vmware and minigw > to save my skin. > > Seems this getline() breaks quite a lot and I am not quite sure this is > _very_ positive for cygwin. People just get left alone in the dark (no > everybody can debug and patch) and the pride of cygwin is somehow self > focused. I would expect such dramatic moves to be done with more care. > Otherwise I could call cygwin nice, but not reliable. I like this slogan: "Cygwin: nice, but not reliable". We should adopt this, and refer 90% of the mailing list complaints to it. :-) 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! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/