X-Spam-Check-By: sourceware.org Message-ID: <4418AB38.B7D87B36@dessent.net> Date: Wed, 15 Mar 2006 16:03:04 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: GCC 4.x+ References: 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 Angelo Graziosi wrote: > I have built GCC-3.4.6, 4.0.3, 4.1.0 in this way (using the Cygwin > GCC-3.4.4-1): > > ./configure --prefix=/usr/local/gcc-3.4.6 (or 4.0.3, 4.1.0) > make > make install I like to use --enable-version-specific-runtime-libs because it seems cleaner and that's the way the Cygwin gcc packages do it. I also use --disable-nls since I don't care for those dozens of various message catalog files for languages I don't speak. You will also need --enable-sjlj-exceptions if you ever plan to compile code that could throw an exception inside a stack frame containing foreign (non-DW2-enabled) compiled code, such as a win32 callback. This can be common in win32 GUI applications, but not an issue if you don't use C++ exceptions and/or you don't write code that could be called from a win32 callback. The dwarf2 EH is a lot faster too. 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/