Re: Libtool problems when building ImageMagick

2008-03-18 Thread Corinna Vinschen 
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/ml/cygwin-apps/2008-02/msg00131.html
  http://cygwin.com/ml/cygwin-apps/2008-02/msg00189.html
  http://cygwin.com/ml/cygwin-apps/2008-03/msg00059.html
  http://cygwin.com/ml/cygwin-apps/2008-03/msg00254.html

What do I have to do to get your attention?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

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

Re: Libtool problems when building ImageMagick

2008-03-17 Thread Volker Quetschke 

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


Thanks Yaakov,

I actually tried


NO_LIBTOOLIZE=1


this before, but it somehow didn't help ;)


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


With this IM builds :)

  Volker




Yaakov




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




--
= http://wiki.services.openoffice.org/wiki/Debug_Build_Problems  =
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature

Re: Libtool problems when building ImageMagick

2008-03-17 Thread Yaakov (Cygwin Ports) 

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

Re: Libtool problems when building ImageMagick

2008-03-17 Thread Volker Quetschke 

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.


I didn't try without cygautoreconf, cygport insists (hardcoded) on using
--force in the autoreconf command. Using the following patch

--- /usr/bin/cygport.org2008-03-17 17:30:33.745423700 -0400
+++ /usr/bin/cygport2008-03-17 17:17:50.856572500 -0400
@@ -976,7 +976,7 @@

export WANT_AUTOCONF=${WANT_AUTOCONF:-2.5};
export WANT_AUTOMAKE;
-   /usr/bin/autoreconf --force -i --verbose || error "autoreconf 
failed"

+   /usr/bin/autoreconf -i --verbose || error "autoreconf failed"

for d in . ${ac_subdirs}
do

leads to a successful build of ImageMagick.

  Volker



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/





--
= http://wiki.services.openoffice.org/wiki/Debug_Build_Problems  =
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature

Re: Libtool problems when building ImageMagick

2008-03-17 Thread Brian Dessent 
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/

Libtool problems when building ImageMagick

2008-03-17 Thread Volker Quetschke 

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






The `cygport ImageMagick-6.3.9.8-1 prep` works as usual (with the
accordingly adjusted files) but `cygport ImageMagick-6.3.9.8-1 compile`
fails with a libtool error like this:


./libtool: line 845: X--tag=CC: command not found
(rest deleted)

See here

for the full logfile.

This does not happen with the ImageMagick 6.3.6-3 release (thanks
Yaakov) but with the latest versions of IM.

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.

If it helps, my cygcheck output:


I would like to release a new IM package, but currently I am stuck.

  Volker


--
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D



signature.asc
Description: OpenPGP digital signature