X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Message-ID: <47DF2154.3@users.sourceforge.net>
Date: Mon, 17 Mar 2008 20:56:36 -0500
From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Libtool problems when building ImageMagick
References: <47DEBD48.6060102@scytek.de> <47DEC5DA.735CB772@dessent.net>
In-Reply-To: <47DEC5DA.735CB772@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Brian Dessent wrote:
| Anyway, since this bundled libtool looks like it's very recent it
| doesn't make sense to try to forcibly autoreconf it to something older,
| as cygautoreconf seems to want to run autoreconf --force.  Normally
| autoreconf would only run libtoolize if it looks like something needs
| updating.  So I guess what I'm saying is just remove cygautoreconf from
| your cygport, or if it's needed for some reason, don't run --force.

NO_LIBTOOLIZE=1

(fix for typo just checked into CVS; use "export LIBTOOLIZE=true" as a
backup until 0.3.9)


Yaakov


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH3yFUpiWmPGlmQSMRCK5AAKDvbpz0sVa7SYA5qXDQuFkxU4pFvwCgl9OH
53A3WFr7blMMEP5PPJL01CA=
=GQ9F
-----END PGP SIGNATURE-----

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

