[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

2.52g: config.log and --with args

From: Jeff Squyres
Subject: 2.52g: config.log and --with args
Date: Mon, 12 Nov 2001 12:20:13 -0500 (EST)

It seems that the output of the command line used to invoke ./configure in
config.log does not quote multi-word tokens properly.  This problem exists
in 2.52, so I did a CVS checkout of autoconf this morning (12 Nov 2001 --
2.52g) and the problem still exists.

This did work properly in the config.status output in autoconf 2.13.

This is annoying because it prevents direct cut-n-pasting of the command
line from the config.log file to a command line to re-invoke ./configure
with the same arguments.

Here's an example.  If I invoke the following from the command line:

$ ./configure --with-someflag="foo bar baz" --with-otherflag=blah

The config.log (2.52g) file shows:

  $ ./configure --with-someflag=foo bar baz --with-otherflag=blah

Notice that "bar" and "baz" show up as separate arguments -- they are not
associated with the --with-someflag argument.  However, when using
autoconf 2.13 with the same command line, the config.status file reads:

# ./configure  '--with-someflag=foo bar baz' --with-otherflag=blah

>From the quoting, it seems clear that 2.13 recognized that the $withval of 
someflag was multi-token, and therefore was quoted.  otherflag, however, 
was only a single token, and was therefore not quoted.

Can this kind of behavior be added to 2.52g?


{+} Jeff Squyres
{+} address@hidden
{+} Perpetual Obsessive Notre Dame Student Craving Utter Madness
{+} "I came to ND for 4 years and ended up staying for a decade"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]