Hi!
>>> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
[...]
Pavel> # m4_unquote(STRING)
Pavel> # --
Pavel> # Remove one pair of the quotes if they exist
[...]
This just recall me of a place where I would like quotes not
to be removed...
I'd like to use AC_HELP_STRING t
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_
On Thu, Feb 15, 2001 at 08:47:54PM -0500, Pavel Roskin wrote:
: Hello, Lars!
: > This patch removes a race condition in config.status.
:
: Neighter configure nor config.status should be run in the same time in the
: same directory. Please explain why you have to.
I use config.status to generate
The autoscan from autoconf-2.49c has ugly output for the
missing macro warning.
$ ../../devel/bin/autoscan.orig
warning: missing AC_TYPE_PID_T wanted by: libsdptk/src/PGS_IO_Gen_Temp_Reference.c:675
libsdptk/src/PGS_SMF_Comp.c:5336 libsdptk/src/PGS_SMF_Comm.c:139
libsdptk/smfcompile/PGS_SMF_Co
> I am wondering if the new preferred way of an empty AC_OUTPUT
> and use of AC_CONFIG_FILES in autoconf-2.49c is presently
> known to automake-1.4d or does automake still require the
> old way of doing AC_OUTPUT. Thanks.
CVS automake, and 1.4d too I believe, should support both the
old and the n
I am wondering if the new preferred way of an empty AC_OUTPUT
and use of AC_CONFIG_FILES in autoconf-2.49c is presently
known to automake-1.4d or does automake still require the
old way of doing AC_OUTPUT. Thanks.
Paul
On Feb 15, 2001, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Hello, Lars!
>> This patch removes a race condition in config.status.
> Neighter configure nor config.status should be run in the same time in the
> same directory. Please explain why you have to.
It's certainly valid to have multiple s
Hello, Alexandre!
> > Hello, Lars!
> >> This patch removes a race condition in config.status.
>
> > Neighter configure nor config.status should be run in the same time in the
> > same directory. Please explain why you have to.
>
> It's certainly valid to have multiple simultaneous config.status
>
On Feb 16, 2001, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> I see. But we don't need reentrancy for configure, do we?
Nope. Not even for config.status, AFAIK. We just need concurrency,
not reentrancy. Unless a new requirement has entered the picture.
--
Alexandre Oliva Enjoy Guarana', see
On 16 Feb 2001, Alexandre Oliva wrote:
> On Feb 16, 2001, Pavel Roskin <[EMAIL PROTECTED]> wrote:
>
> > I see. But we don't need reentrancy for configure, do we?
>
> Nope. Not even for config.status, AFAIK. We just need concurrency,
> not reentrancy. Unless a new requirement has entered the pi
Unless, I am reading the manual (2.49c) wrong the following is
prefered:
AC_CONFIG_AUX_DIR([config])
to
AC_CONFIG_AUX_DIR(config)
With automake-1.4d, in the first case the configure directory is
`[config]' rather than `config'.
$ ../../devel/bin/automake
automake: configure.ac: required file
> "Paul" == Paul Martinolich <[EMAIL PROTECTED]> writes:
Paul> AC_CONFIG_AUX_DIR([config])
Paul> With automake-1.4d, in the first case the configure directory is
Paul> `[config]' rather than `config'.
I just checked in a fix for this. It was waiting for copyright
paperwork which was approv
Hello!
It arrepars that the problem that I originally attributed to the "-Wall"
processing has to do with the way how AC_OUTPUT is defined. I expected a
message about AC_OUTPUT with arguments, and was surprised not to see it.
acgeneral.m4 defines AC_OUTPUT twice - once by AU_DEFUN, then by
m4_de
13 matches
Mail list logo
