X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <47FC0DA6.1080208@cwilson.fastmail.fm>
Date: Tue, 08 Apr 2008 20:28:22 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Attn: cygport maintainer [was: Re: Libtool 2.2.2]
References: <47F6A816 DOT 2010208 AT alice DOT it> <47F73BA6 DOT 6000001 AT alice DOT it> <47F7E1D1 DOT 804DF919 AT dessent DOT net> <47F94F88 DOT 6050705 AT cwilson DOT fastmail DOT fm> <47F9A114 DOT 3060608 AT users DOT sourceforge DOT net> <47F9B6B6 DOT 4090908 AT cwilson DOT fastmail DOT fm> <47FA254B DOT 205 AT users DOT sourceforge DOT net> <47FB0E98 DOT 3060402 AT cwilson DOT fastmail DOT fm> <47FB25D3 DOT 6040703 AT users DOT sourceforge DOT net> <47FB83D4 DOT 5080600 AT cwilson DOT fastmail DOT fm> <47FBF68C DOT 6070709 AT users DOT sourceforge DOT net>
In-Reply-To: <47FBF68C.6070709@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Yaakov (Cygwin Ports) wrote:
> Charles Wilson wrote:
> | I'm not so sure. I still think that calling LT_OUTPUT immediately after
> | LT_INIT is not exactly equivalent to 1.5 behavior.
> 
> I think it is equivalent, seeing from a typical configure run with
> libtool 1.5:
> 
> Looking at some of the other compatibility macros, how about the
> following instead:
> 
> AU_DEFUN([AC_PROG_LIBTOOL],
> [LT_INIT
> LT_OUTPUT
> AC_DIAGNOSE([obsolete],
> [$0: Remove this warning and the call to LT_OUTPUT if you do not need
> libtool to exist before AC_OUTPUT.])
> ])
> 
> AU_ALIAS([AM_PROG_LIBTOOL], [AC_PROG_LIBTOOL])

That looks OK to me. I'll include something like this in the next 
version of libtool2.2 (or "libtool" test: 2.2).

> | [*] But again, my recommedation is that cygport should NOT run
> | autoupdate in an automated way. Instead, the package maintainer should
> | run it, inspect the results, and fold those changes into .src.patch.
> 
> Agreed.
> 
> | m4_include([libtool.m4])
> | m4_include([ltoptions.m4])
> | m4_include([ltversion.m4])
> | m4_include([ltsugar.m4])
> | m4_include([lt~obsolete.m4])
> 
> While that makes sense, I doubt that would work with the special build
> systems that I'm discussing, at least not in an automated way without
> patching those build systems more than necessary.  I have something else
> in mind, but I'll need to try it out first.

For your packages, do whatever makes your life easier. <g>

> | Sure...just waiting for more input.
> 
> Could you post the answer on cygwin-apps?

Sure.

--
Chuck

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