Message-ID: <437AD581.2090204@cwilson.fastmail.fm>
Date: Wed, 16 Nov 2005 01:45:21 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: autoconf AC_CONFIG_FILES Macro Issues
References: <loom DOT 20051116T024708-407 AT post DOT gmane DOT org>
In-Reply-To: <loom.20051116T024708-407@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Larry Adams (The Cacti Group) wrote:

> I have an issue with both the autoconf AC_CONFIG_FILES and AC_CONFIG_COMMANDS 
> MACROS in the current 2.59 version of autoconf.  When compiling 
> the ./configure shell script, the use of these macros prepents each command 
> with several white spaces causing the use of continuation characters within 
> the resulting ac_config_files and ac_config_commands to fail during subsequent 
> execution of the configure script.
> 
> In the case of the AC_CONFIG_FILES MACRO, there are over 300 space characters 
> prepended on the output line prior to the command being issued.
> 
> My question is, how do I get this logged as a bug?

This is not a cygwin-specific behavior.  You should report this as a big 
to the   bug dash autoconf at gnu dot org   mailing list.

--
Chuck


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