From xemacs-m  Sat Apr  5 17:52:44 1997
Received: from mecca.spd.louisville.edu (mecca.spd.louisville.edu [136.165.40.148])
	by xemacs.org (8.8.5/8.8.5) with SMTP id RAA23258
	for <xemacs-beta@xemacs.org>; Sat, 5 Apr 1997 17:52:43 -0600 (CST)
Received: (from tjchol01@localhost) by mecca.spd.louisville.edu (950413.SGI.8.6.12/8.6.12) id XAA02859; Sat, 5 Apr 1997 23:52:28 GMT
Date: Sat, 5 Apr 1997 23:52:28 GMT
Message-Id: <199704052352.XAA02859@mecca.spd.louisville.edu>
From: "Tomasz J. Cholewo" <tjchol01@mecca.spd.louisville.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: XEmacs-Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: 20.1-b11 build success sparc-sun-solaris2.5
In-Reply-To: <rvu3llt7s9.fsf@sdnp5.ucsd.edu>
X-Mailer: VM 6.23 under 20.1 XEmacs Lucid (beta11)

David Moore wrote:
> I notice that we output $configure_args, which can be ambigious.  For
> example, did I use '--cflags=-g -O2' or '--cflags=-g' '-O2'.
> 
> I also notice that  `./config.status --recheck' has the same problem. We
> should be using $quoted_arguments not $configure_args for these things.
> Although the current building of $quoted_arguments also isn't perfect
> (in a different way).  Patch for both in separate mail.

$configure_args were chosen for an Installation file for purely
aesthetic reasons.  As I understand, it is not supposed to be ``machine
readable'' anyway so there is not too much place for real ambiguity.

Tom

