X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Shankar Unni Subject: Re: Some notes on building gcc-4.3.0 Date: Mon, 18 Jun 2007 13:19:04 -0700 Lines: 24 Message-ID: References: <466F9B52.1000709@cwilson.fastmail.fm> <4672C1F4.6010306@users.sourceforge.net> <46736405.2010303@cwilson.fastmail.fm> <4673E461.80960A59@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666 In-Reply-To: <4673E461.80960A59@dessent.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Brian Dessent wrote: > Does this mean that we'll start to libgcc_s.dll's sprouting like > mushrooms in the install dirs of various apps, or in *gasp* > %WINDIR%/system32 over the coming years? Is this library versioned at > all? What about conflicts? You already see the effects of this in the Linux world, with the more recent distributions having to ship a set of compat_libgcc_blah packages for each major (ABI-incompatible) previous release going back (they're on 4.1/4.2 these days, and there's one for 3.3 and one for 2.9). And most commercial/non-free software shipped on Linux (e.g. Oracle, Java, ..) just states explicitly which packages they depend on. So if I may offer a blueprint going forwards: * introduce a libgcc_something package containing the latest DLLs/.so's, and include it in the Base package. * later, if these are ever incompatibly ABI-rev'ed, switch the default distribution to the new version, and introduce a compat-libgcc-* package for the old version (which preserves their filename), and include that in the Libs package. -- 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/