Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com To: cygwin-apps AT cygwin DOT com Subject: pregerenated cinstall/configure broken in cvs Organization: Jan at Appel Mail-Followup-To: cygwin-apps AT cygwin DOT com From: Jan Nieuwenhuizen Date: Tue, 29 Jan 2002 11:46:23 +0100 Message-ID: Lines: 43 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi, I've sent a patch a while ago that included a 'fix' for cinstall/configure.in wrt CFLAGS; but I could not reproduce the error, so it was removed. It turns out that the pregenerated configure in cinstall is buggy. Can someone check in a freshly generated configure? After a fresh checkout, I get: 11:32:51 fred AT appel:~cinstall$ MINGW32=yes CFLAGS='-mno-cygwin' ./configure creating cache ./config.cache checking host system type... powerpc-unknown-linux-gnu checking target system type... powerpc-unknown-linux-gnu checking build system type... powerpc-unknown-linux-gnu checking for gcc... gcc checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for g++... g++ ./configure: CFLAGS: command not found Running autoconf makes this go away (no patch needed), that's why we couldn't reproduce it. Here's a snippet of the pre/post autoconf diff: diff -u ../cinstall.orig/configure . [..] @@ -886,7 +875,7 @@ test -z "$CC" && { echo "configure: error: no acceptable cc found in \$PATH" 1>&2; exit 1; } fi -CXXFLAGS="$(CFLAGS)" +CXXFLAGS='$(CFLAGS)' if test "$program_transform_name" = s,x,x,; then Greetings, Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org