To: cygwin AT cygwin DOT com
From: Larry Adams =?utf-8?b?KFRoZQ==?= Cacti =?utf-8?b?R3JvdXAp?= <larryjadams AT comcast DOT net>
Subject:  autoconf =?utf-8?b?QUNfQ09ORklHX0ZJTEVT?= Macro Issues
Date: Wed, 16 Nov 2005 01:52:35 +0000 (UTC)
Lines: 16
Message-ID:  <loom.20051116T024708-407@post.gmane.org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
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

Hi,

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?

Larry Adams
The Cacti Group 


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