X-Spam-Check-By: sourceware.org Message-ID: <44513EE5.53E528AB@dessent.net> Date: Thu, 27 Apr 2006 15:00:05 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Fixing the state of C++ in Cygwin References: <000001c669f1$88a72cd0$a501a8c0 AT CAM DOT ARTIMI DOT COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Dave Korn wrote: > This sounds like an error in your configure arguments getting transcribed > into the generated makefiles to me. It's not an extra '&& )', it's something > missing between the '&&' and the ')' that's the real problem, and that > probably happened because a shell variable used to generate the output from > that stage of configure ended up being empty because of a failure of a > pattern-match earlier on because of a mis-spelt option. (Well, for example.) > Configure scripts aren't terribly robust against syntax issues and > metacharacters, let's just hope nobody ever invents a target triplet with > backtick-rm-dash-rf-star-backtick in it![*] I think this is one of those "generic build script used to be written for ash but now sh is bash" problems that have been reported on other GBS script packages recently. > You probably shouldn't be patching anything at all. Gcc should build for > cygwin OOTB; there are cygwin-specific patches that add things like > -mno-cygwin, but the basic compiler should be fine as it stands. -mno-cygwin ought to work fine from the stock FSF sources I'm told (provided of course that you build it twice, once as i686-pc-cygwin and then again as i686-pc-mingw and install them to the same prefix.) Brian -- 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/