X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48CA3826.9050608@users.sourceforge.net> Date: Fri, 12 Sep 2008 04:36:38 -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] New experimental package: gcc4-4.3.0-1 References: <48C8FE4D DOT 1090103 AT users DOT sourceforge DOT net> <013401c9140b$22b569c0$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48CA2107 DOT FE8D0CB2 AT dessent DOT net> In-Reply-To: <48CA2107.FE8D0CB2@dessent.net> 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 Brian Dessent wrote: > Please don't. gcc isn't special in this regard, it shouldn't receive > any special treatment. bash fails without cygintl-8.dll and I don't > think anyone is proposing to statically link libintl into bash just > because some people seem to find ways to screw up their installations by > not installing libintl8. If there's a problem we need to fix the root > cause, not paper it over. Agreed. BTW, I noticed that gcc builds with static libintl/libiconv (the standard config.rpath flaw); low priority, but I really don't like static linking unless absolutely necessary. > IMHO, despite the above we should still ship shared libstdc++ even if > it's not the default -- though I would even argue that we should go one > step farther and make it the default and say that if you need to > override operator new you select the static libstdc++. I admit to know very little about C++; how often would this happen? > Otherwise, we just get ourselves into ABI compatibility > hell because every C++ library gets a copy of libstdc++ linked > into it, which means they are tied to the compiler version. > As it is now we are going to have to rebuild all > libstdc++-using code in the distro with the new compiler because up > until now we had no choice but static libstdc++, but by not stopping > this insanity now we only prolong it. Which is the current situation. YA reason I think that gcc-4.3 should be limited to release-2, and that everything should be rebuilt with it for 1.7. > Should work fine. Requires explicit --enable-libgomp though (not > enabled by default.) I've seen a *small* number of packages using it so far, so it would be nice to try. But we'll need autoconf-2.62 as well. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkjKOCYACgkQpiWmPGlmQSNC1gCgymaPY6yNcOjoy5yxzTEGRBuO aM8An1idh88XN7NuLHmlvVwtM4UiExKY =aUiR -----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/