X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48CD7C05.5070607@users.sourceforge.net> Date: Sun, 14 Sep 2008 16:03:01 -0500 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated experimental package: gcc4-4.3.2-1 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave Korn wrote: > The main purpose of this update is to resolve the packaging conflict between > the original native Cygwin gcc-3.4.4 and this new package, which it does by > appending a version suffix. "gcc.exe" is now "gcc-4.exe", "g++.exe" becomes > "g++-4.exe", and so on. While this is fine for an experimental package, I think we need to consider switching to gcc4 as the default for 1.7. > Finally, I have removed the controversial "-mno-cygwin" flag. Hooray!! > If there's anything else you think is important, please contact the Cygwin > mailing list with your suggestion. * Override LIBINTL and LIBICONV during make with dynamic linking * libssp: Is it used? Should it also be dynamic? * Are GPC and/or GDC available yet for gcc-4.3? When you "deforkify" the cygport you're using, is there any way others can help? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkjNfAUACgkQpiWmPGlmQSNaFACeJJwXDLtNLVMsYG0YZU4IEfQY AjUAn2ndTvQ88pWw1TxGTPWWhjdfZO3M =S9dR -----END PGP SIGNATURE----- -- 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/