From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8959 invoked by alias); 28 Oct 2008 02:28:49 -0000 Received: (qmail 8948 invoked by uid 22791); 28 Oct 2008 02:28:48 -0000 X-Spam-Check-By: sourceware.org Received: from mail-gx0-f19.google.com (HELO mail-gx0-f19.google.com) (209.85.217.19) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 28 Oct 2008 02:27:53 +0000 Received: by gxk12 with SMTP id 12so3407215gxk.2 for ; Mon, 27 Oct 2008 19:27:51 -0700 (PDT) Received: by 10.65.160.7 with SMTP id m7mr7304173qbo.16.1225160870743; Mon, 27 Oct 2008 19:27:50 -0700 (PDT) Received: from ?192.168.0.100? (S0106001346f94b85.wp.shawcable.net [24.76.249.6]) by mx.google.com with ESMTPS id s12sm1519935qbs.9.2008.10.27.19.27.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 27 Oct 2008 19:27:49 -0700 (PDT) Message-ID: <490678A4.40908@users.sourceforge.net> Date: Tue, 28 Oct 2008 02:28:00 -0000 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: SECURITY vulnerabilities update 2007-Sep-25 References: <48DC650B.7040407@users.sourceforge.net> <20081027091918.GA28578@calimero.vinschen.de> <49066DF4.2000108@cwilson.fastmail.fm> In-Reply-To: <49066DF4.2000108@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-10/txt/msg00084.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charles Wilson wrote: > So...should cygwin-1.7 packages all be built using gcc-4.x, or not? (And > is it really, as I fear, an all-or-nothing proposition given the libgcc > changes?) I'm not sure how much this is all-or-nothing for C, but I imagine that it would be for C++. But I very seriously think that everything should be rebuilt with cygwin-1.7 and gcc-4.3, as this is the best time to make that transition (as well as give both a through testing before stabilizing). Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkGeKQACgkQpiWmPGlmQSOxDgCffuHEKcj+Cvl+r8i8f79ikqpE F9QAoL1qX9Qa5wuF3n7Nq2TJ1VSOUOOQ =CXoy -----END PGP SIGNATURE-----