From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15965 invoked by alias); 8 May 2007 06:16:09 -0000 Received: (qmail 15947 invoked by uid 22791); 8 May 2007 06:16:08 -0000 X-Spam-Check-By: sourceware.org Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.168) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 08 May 2007 06:16:02 +0000 Received: by ug-out-1314.google.com with SMTP id s2so35781uge for ; Mon, 07 May 2007 23:16:00 -0700 (PDT) Received: by 10.67.100.17 with SMTP id c17mr274031ugm.1178604960094; Mon, 07 May 2007 23:16:00 -0700 (PDT) Received: from scientist.mobile.usilu.net ( [195.176.176.226]) by mx.google.com with ESMTP id 27sm143660ugp.2007.05.07.23.15.54; Mon, 07 May 2007 23:15:56 -0700 (PDT) Message-ID: <46401599.7000705@lu.unisi.ch> Date: Tue, 08 May 2007 06:16:00 -0000 From: Paolo Bonzini Reply-To: bonzini@gnu.org User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Charles Wilson CC: Steve Ellcey , binutils@sourceware.org, gcc-patches@gcc.gnu.org, gdb-patches@gcc.gnu.org, newlib@sourceware.org Subject: Re: Patch to update libtool in GCC and Src trees References: <463F6F90.4080401@cup.hp.com> <463F873D.5000706@lu.unisi.ch> <463FF2AE.3000503@cwilson.fastmail.fm> In-Reply-To: <463FF2AE.3000503@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-05/txt/msg00508.txt.bz2 > Either way, Steve's existing patch needs to be extended to do > _something_ with newlib, and that means a few more days of shakedown so > the linux-native-newlib guys can test it. Agreed. > Ralf W. and I have been working on some refinements for cygwin/mingw > libtool in libtool's ToT over the last few weeks. They are not yet > ready, and I certainly do not want to hold back gcc progress waiting on > libtool: the 20070318 libtool ToT included in Steve's update works fine > as demonstrated above. However, now that Steve's done all or most of > the _hard_ work, what will be the policy going forward with regards to > updating external, but embedded, tools like libtool? > > How often will gcc re-import the latest libtool ToT? Any chance of > another -- less disruptive! -- update before 4.THREE.0 ships? If it were only for me, we could commit to syncing libtool ToT periodically at least until libtool 2.0 is out. But I suspect that to convince everybody, libtool would need a more precise notion of stable-ness. After that, it will be the usual mess, the same as for Autoconf and Automake... :-) Paolo