delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
From: | Shankar Unni <shankarunni AT netscape DOT net> |
Subject: | Re: Some notes on building gcc-4.3.0 |
Date: | Mon, 18 Jun 2007 13:19:04 -0700 |
Lines: | 24 |
Message-ID: | <f56pbr$mql$1@sea.gmane.org> |
References: | <466F9B52 DOT 1000709 AT cwilson DOT fastmail DOT fm> <4672C1F4 DOT 6010306 AT users DOT sourceforge DOT net> <46736405 DOT 2010303 AT cwilson DOT fastmail DOT fm> <4673E461 DOT 80960A59 AT dessent DOT net> |
Mime-Version: | 1.0 |
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 AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |