X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Message-ID: <493ECBA2.EA3D7E93@dessent.net>
Date: Tue, 09 Dec 2008 11:48:50 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Latest autoconf (2.63): problem generating libtool script when   reconfiguring GCC (maybe others).
References: <2ca21dcc0812091011t544f1a12hf920d85359131ea2@mail.gmail.com> <loom.20081209T191414-825@post.gmane.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Eric Blake wrote:

> Oops.  m4_append was undocumented in 2.60, then changed semantics in autoconf
> 2.62.  Newer libtool works around the semantic change by using lt_append, not
> m4_append:
> http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=commitdiff;h=5b560bd
> 
> But you still have the definition of lt_if_append_uniq from older libtool,
> which doesn't work with newer autoconf.  I guess this means no one has yet
> identified this as one of the fixes that needs to be imported as part of future-
> proofing the gcc tree to make the eventual transition to newer autotools
> easier.  Do you feel like opening a gcc incident with this email chain as the
> starting point?

This is already fixed on the gcc mainline, which has ltsugar.m4 serial
6, from libtool 2.2.6.

As to the version check, that's another thing that is not on the 4.3
branch but is present on mainline (see config/override.m4.)

Brian

--
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/

