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 Date: Tue, 16 Mar 2004 11:39:27 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: using gcc 3.3.3 Message-ID: <20040316163927.GC21715@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Mar 16, 2004 at 10:49:20AM -0000, Ben DOT Taylor AT provident DOT co DOT uk wrote: >Thanks. I seemingly compiled gcc 3.4 20040310 successfully, once I had >installed bison and flex into cygwin. I'm going to try the decisive test >tonight which will be to rename all the g++ files other than the one in >gcc_34 directory, compile a C++ program, then rename the cygwin1.dll to >cygwin2.dll, then try to run the program. If it runs, I've got gcc 3.4 >working correctly. This way, I know that the gcc 3.4 is definitely the only >one being used, and that it's not relying on cygwin for the program to run >(although it is to run the compiler). > >Now... is it possible to use -mno-cygwin on the compiler *itself*..., maybe? If it was, that would certainly be self-selectingly off-topic for this *cygwin* list since one of the main points of cygwin is to provide an environment for building GNU tools like GCC. You may want to check out the mingw lists at www.mingw.org which deal with non-cygwin versions of GNU tools. -- Christopher Faylor Cygwin Project Leader Red Hat, Inc. -- 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/