Re: Libtool problems when building ImageMagick

Yaakov, On Mar 17 20:56, Yaakov (Cygwin Ports) wrote: > NO_LIBTOOLIZE=1 > > (fix for typo just checked into CVS; use "export LIBTOOLIZE=true" as a > backup until 0.3.9) > > > Yaakov Is there any reason why you don't reply to me on the cygwin-apps mailing list for a month now? http://cygwin.com

Re: Libtool problems when building ImageMagick

Yaakov (Cygwin Ports) wrote: 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 libtool

Re: Libtool problems when building ImageMagick

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

Re: Libtool problems when building ImageMagick

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

Re: Libtool problems when building ImageMagick

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

Libtool problems when building ImageMagick

I wanted to prepare a new ImageMagick package, but I am stuck with the following problem. It should be easy, its a cygport build with the following files