X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <47C45106 DOT 6090300 AT pobox DOT com> <47C45534 DOT A74427F4 AT dessent DOT net> <6910a60802270735x3441fd76id868f1ebe7a4d89 AT mail DOT gmail DOT com> <47C58CC6 DOT 1F2CFC45 AT dessent DOT net> Subject: RE: Testing gcc 4.2.3 Date: Wed, 27 Feb 2008 16:25:14 -0000 Message-ID: <001e01c8795d$54cb53f0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <47C58CC6.1F2CFC45@dessent.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 27 February 2008 16:16, Brian Dessent wrote: > That would be fine if it were even possible to build a shared libgcc. > FSF gcc won't even do this, nor will it build shared libstdc++, etc. > MinGW's gcc 4.2 has a humongous local patch that backports a bunch of > stuff from 4.3 as well as using an ugly kludge to build shared libgcc. > > I can't speak for Dave or whoever else will spend time maintaining the > Cygwin gcc packages, but I can say that if the past is any indication, > maintaining a huge local out-of-tree patch is a giant pain and causes a) > releases/updates to be slow or nonexistant and b) maintainers to not > want to continune doing their thing. It's for these reasons that I > think we really need to wait until these issues are fixed upstream I'm working on it slowly in the background, owing to not lots of spare time, but my basic plan is to submit patches to get all the support needed into upstream gcc and then release a more-or-less OOTB build for cygwin. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/