On Nov 10, 2000, Paul Eggert <[EMAIL PROTECTED]> wrote:
>> From: Akim Demaille <[EMAIL PROTECTED]>
>> ac_optarg=`expr "x$ac_option" : 'x[^=]*=\(.*\)'`
> Ouch. Can you rewrite that as follows to work around the bug?
How about:
# Work around the problem that "expr 'a' : 'a\(\)'" outputs "0" in
Hi all,
The attached is the result of a few minutes of copying the
current autoconf arguments into AutoOpts form and generating.
It is not a perfect match for what you all want, but close.
Plus, I can generate man pages and info docs
Cheers,
Bruce
acopts.sh
AutoGen Definitions op
> From: Akim Demaille <[EMAIL PROTECTED]>
> Date: 10 Nov 2000 10:28:29 +0100
>
> | The POSIX standard says:
> |
> |Usually, the matching operator shall return a string representing
> |the number of characters matched ('0' on failure). Alternatively,
> |if the pattern contains at leas
> From: Akim Demaille <[EMAIL PROTECTED]>
> Date: 10 Nov 2000 10:23:25 +0100
>
> But our troubles could be worse than this, since `expr' is not used
> only in AS_DIRNAME. For instance any CVS configure contains
>
> ac_optarg=`expr "x$ac_option" : 'x[^=]*=\(.*\)'`
Ouch. Can you rewrite
On Nov 9, 2000, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Hello, Peter!
>> Exactly where do the GNU standards say anything about long option
>> abbreviation?
> Well, whenever I don't check something I'm punished for that :-)
Oops. Ditto :-)
--
Alexandre Oliva Enjoy Guarana', see http://ww
Hello, Akim!
> | By the way, shouldn't we change the syntax of AC_LANG to
> |
> | AC_LANG(C, COMPILERS, ACTION-IF-FOUND, ACTION-IF-NOT-FOUND)
> |
> | and go ahead if no C compiler has been found but ACTION-IF-NOT-FOUND is
> | given?
>
> What advantage would that bring? How do you deal with th
hi Alexandre,
I'm sorry to insist, but we've met this bug several times, and we
never had a clear definition of it. I'd like to fix Autoconf but
understanding why it's fixed :)
The problem with Ultrix is probably that somehow it changes the 8th
bit of the variable values. But `when' is the qu
| Hello, Ralf!
| > checking how to run the C preprocessor... cc -E
| > checking for sh-rtems-gcc... sh-rtems-gcc
|
| It's a separate problem that needs to be addressed before 2.50.
| AC_PROG_CPP should require AC_PROG_CC.
Right.
| Maybe we should go as far as to make both AC_PROG_CPP and AC_PR
| The POSIX standard says:
|
|Usually, the matching operator shall return a string representing
|the number of characters matched ('0' on failure). Alternatively,
|if the pattern contains at least one regular expression
|subexpression "[\(...\)]", the string corresponding to "\1"
> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> How about if we add an AC_PROG_EXPR that searches for a working
Paul> expr and sets EXPR to its value, or to "false" if it can't find
Paul> one. Then AS_DIRNAME_EXPR can AC_REQUIRE([AC_PROG_EXPR]) and
Paul> use "$EXPR" instead of "exp
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> It doesn't mean that we have eliminate all common code right
Pavel> now, but it would be nice to start the conversion process now,
Pavel> e.g. with the option parcer.
We have to finish M4sh first, and extract an autoscript or somet
11 matches
Mail list logo
