X-Spam-Check-By: sourceware.org Message-ID: <453D9BC6.6000206@byu.net> Date: Mon, 23 Oct 2006 22:51:18 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: another cygport bug Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The check for config_h in cygautoreconf does not work when the line requests a template by a different name, as is the case with coreutils 6.4: $ grep CONFIG_HEADERS coreutils-6.4/configure.ac AC_CONFIG_HEADERS([lib/config.h:lib/config.hin]) $ cygport coreutils-6.4.1 build touch: cannot touch `./lib/config.h:lib/config.hin.in': No such file or directory This patch solves the issue. - --- /bin/cygport.orig 2006-10-23 22:29:18.859375000 -0600 +++ /bin/cygport 2006-10-23 22:43:03.656250000 -0600 @@ -697,7 +697,7 @@ for d in . ${ac_subdirs} do - - config_h="$(grep 'A[CM]_CONFIG_HEADERS*' ${d}/${configure_ac} | sed -e 's!A[CM]_CONFIG_HEADERS*(\[*\(.*\))!\1!g' -e 's!\]*!!g')"; + config_h="$(grep 'A[CM]_CONFIG_HEADERS*' ${d}/${configure_ac} | sed -e 's!A[CM]_CONFIG_HEADERS*(\[*\(.*\))!\1!g' -e 's!\]*!!g' -e 's!:.*!!')"; if [ -n "${config_h}" ] then - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFPZvF84KuGfSFAYARApAQAJ9SopQTuRLxfsFxOPEUvf9CRCTlGQCeJEa6 An2G9Qm3y3R5U89vMrUOPFM= =9xIK -----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/