This patch fixes the config.log problem of overwriting the previous
config.log even if you just invoke configure --help. One problem
remains that should be fixed - the temporary log file (conf-log.tmp)
is left behind in the current directory if you run configure --help,
but should be removed when
Hello, Lars!
> * acgeneral.m4 (_AC_INIT_CONFIG_LOG): New macro.
> (AC_MESSAGE_LOG_NAME): Contains current logfile name. Use it.
> (_AC_INIT_DEFAULT_FDS): Start logging to conf-log.tmp.
> (_AC_INIT): Invoke _AC_INIT_CONFIG_LOG after options have
> been parsed.
I thin
On Thu, Feb 15, 2001 at 08:30:04PM -0500, Pavel Roskin wrote:
: Hello, Lars!
: > * acgeneral.m4 (_AC_INIT_CONFIG_LOG): New macro.
: > (AC_MESSAGE_LOG_NAME): Contains current logfile name. Use it.
: > (_AC_INIT_DEFAULT_FDS): Start logging to conf-log.tmp.
: > (_AC_INIT): Invoke _AC_
Hello, Lars!
> : I think it's an overkill. Errors during option parsing should go to
> : stderr. This would solve the problem.
>
> The config.log file seems so wrong without those parts...
Maybe you mean the parts that are generated _before_ option parsing? I can
understand why they are importan
On Feb 13, 2001, "Lars J. Aas" <[EMAIL PROTECTED]> wrote:
> +rm -f config.log
> +mv AS_MESSAGE_LOG_NAME config.log
> +m4_define([AS_MESSAGE_LOG_NAME], [config.log])dnl
> +exec AS_MESSAGE_LOG_FD>>AS_MESSAGE_LOG_NAME])
On some systems, you can't rename an open file.
Add `exec AS_MESSAGE_LOG_FD >&
On Sat, Feb 17, 2001 at 06:58:58PM -0200, Alexandre Oliva wrote:
: On Feb 13, 2001, "Lars J. Aas" <[EMAIL PROTECTED]> wrote:
:
: > +rm -f config.log
: > +mv AS_MESSAGE_LOG_NAME config.log
: > +m4_define([AS_MESSAGE_LOG_NAME], [config.log])dnl
: > +exec AS_MESSAGE_LOG_FD>>AS_MESSAGE_LOG_NAME])
:
On Feb 17, 2001, "Lars J. Aas" <[EMAIL PROTECTED]> wrote:
> : But I suppose we need some clean-up action for conf-log.tmp.
> Yes. Do you know if configure has many exit points in AC_INIT (so a trap
> should be set up) or if it's just the one after option parsing?
I don't know :-(
I lost track
I agree with Lars we want to keep the log parts, but my suggestion was
to just move the setting up of config.log *after* arguments have been
parsed. AFAIR, it is possible to do so and keeping AC_MSG_ERROR uses
because *now* there is some magic in AC_MSG_ERROR (well the AS stuff).
I dislike the
