X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <47DEC5DA.735CB772@dessent.net>
Date: Mon, 17 Mar 2008 12:26:18 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Libtool problems when building ImageMagick
References: <47DEBD48 DOT 6060102 AT scytek DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Volker Quetschke wrote:

> The problem in libtool (line 845 and others) is that instead of
> echo, $echo is used. So the env. var echo is supposed to be set, but
> it didn't happen. Why? I know nearly nothing about libtool, so far
> it just worked.

I don't think it's a problem with echo per se, it's a mismatch of
libtool versions.  ImageMagick seems to ship with a bleeding edge
version of libtool bundled in m4/.  However when cygautoreconf runs
autoreconf (which in turn runs libtoolize --copy --force --ltdl) the
libtoolize from the current Cygwin package (1.5.25a-1) is what is run
and it seems to update only the config/ltmain.sh, in essence downgrading
it but leaving the bleeding edge version of m4/libtool.m4 untouched.  So
you end up with a ltmain.sh from 1.5 and a libtool.m4 from 2.3a, and
they disagree on things like how to do handle echo apparently.

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.

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/