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 To: cygwin AT cygwin DOT com, "Gerrit P. Haase" Subject: Re: maintaner of gcc Mail-Copies-To: never Reply-To: sds AT gnu DOT org X-Attribution: Sam X-Disclaimer: You should not expect anyone to agree with me. From: Sam Steingold In-Reply-To: <182221237692.20040716005804@familiehaase.de> (Gerrit P. Haase's message of "Fri, 16 Jul 2004 00:58:04 +0200") References: <000001c469eb$7b529fe0$6501a8c0 AT BOBBYJUNIOR> <116186838409 DOT 20040715152445 AT familiehaase DOT de> <182221237692 DOT 20040716005804 AT familiehaase DOT de> Mail-Followup-To: cygwin AT cygwin DOT com, "Gerrit P. Haase" Date: Fri, 16 Jul 2004 09:01:27 -0400 Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain > * Gerrit P. Haase [2004-07-16 00:58:04 +0200]: > > Sam schrieb: > >>> * Gerrit P. Haase [2004-07-15 15:24:45 +0200]: >>> >>> What is wrong with 3.3.x release series? Are there any serious bugs? >>> Are there issues (for you)? Why do you need 3.4.x? > >> g++ 3.3 cannot compile CLISP. >> it is alleged that g++ 3.4 can. > >> (either version of gcc can compile CLISP, but g++ compile is necessary >> for some extra bug detection). > > > Which version exactly? Is this also true for 3.3.4? How do you build > the packages for the Cygwin release? Any gcc (2.95, 3.0, 3.1, 3.2, 3.3, 3.4) can compile CLISP, that's how I build packages, that's how it is supposed to work. Building with g++ is a way to detect internal CLISP errors, not build production executables. g++ 3.3 cannot build CLISP due to a bug in g++. this bug is allegedly fixed in 3.4. -- Sam Steingold (http://www.podval.org/~sds) running w2k (let((a'(list'let(list(list'a(list'quote a)))a)))`(let((a(quote ,a))),a)) -- 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/