Re: [PATCH] Generalize GNUmakefile, ...

Eric Blake <[EMAIL PROTECTED]> writes: > Is it worth trying to re-merge these two approaches, since they forked > from a common ancestor? I think that was always the intent. I tried to merge them a while back but lacked the time to get it right. > We'd have to figure out how to choose between t

Re: AC_TYPE_SIGNAL obsolete?

Eric Blake <[EMAIL PROTECTED]> writes: > 2008-06-09 Eric Blake <[EMAIL PROTECTED]> > > + Mark AC_TYPE_SIGNAL as obsolete. Thanks for doing this; it makes sense to me. Signal handlers returning 'int' became obsolete on all C platforms as of the first C standard in 1989. In practice they

Re: interrupt causes parse error in configure script

Eric Blake <[EMAIL PROTECTED]> writes: > $ ksh -c 'if test `sleep 5; echo hi` = hi ; then echo yes; fi' > ^Cksh: test: hi: unexpected operator/operand I've also observed this problem. More generally, I've seen ^C not interrupt 'configure' scripts properly, in ways other than what Jim is fixing h

Re: [PATCH] more cleanup before adding shell functions

Eric Blake <[EMAIL PROTECTED]> writes: > Since AS_BASENAME is undocumented, and since it is most useful in variable > assignments, perhaps it is time to redefine it as follows (untested) > > # AS_BASENAME(var, name, [ext]) > # - > # Compute the basename of NAME, with t

Re: avoid spurious failures from MacOS readdir bug

Eric Blake <[EMAIL PROTECTED]> writes: > Is 'ls -1' really non-portable, or is the manual missing '1' from its list of > portable options? Is there any known ls where 'ls -1 | blah' and 'ls | blah' > behave differently? I don't know of any, except where users (mistakenly) define their own "ls"

Re: AC_INIT regression

On 07/11/10 00:45, Paolo Bonzini wrote: > I think it's not too bad to _document_ the change and apply > this patch for 2.68 or 2.69 if we get many complaints (which I doubt > we'll get). That sounds reasonable to me as well. It's important to get 2.67 out fairly soon, since the "int *" bug is rel

Re: Allow inspecting AC_PREPROC_IFELSE output in true branch.

On 07/19/10 10:43, Ralf Wildenhues wrote: > IMHO the most dangerous bit of this patch is that I'm unsure why > AC_EGREP_CPP (aka AC_PROGRAM_EGREP earlier) was introduced in the first > place, if there was some portability issue formerly that prevented an > AC_TRY_PREPROC or so. No, I expect that

Re: [PATCH 1/2] docs: mention cd limitation

On 08/02/10 07:18, Paolo Bonzini wrote: > The only problematic platform seems to be Ultrix, but didn't the Ultrix > shell even lack shell functions? I believe you're right. If we're assuming shell functions, we might as well assume ${var:-val}. I think Ultrix was last released in 1995 and last s

Re: document $at_status for use in RUN-IF-{PASS,FAIL} of AT_CHECK

On 08/20/2010 09:51 PM, Ralf Wildenhues wrote: Would you accept a patch to document $at_status being usable in the RUN-IF-FAIL and RUN-IF-PASS arguments of AT_CHECK (including coverage of course)? That sounds good to me.

Re: document $at_status for use in RUN-IF-{PASS,FAIL} of AT_CHECK

On 08/20/2010 09:51 PM, Ralf Wildenhues wrote: Would you accept a patch to document $at_status being usable in the RUN-IF-FAIL and RUN-IF-PASS arguments of AT_CHECK (including coverage of course)? I think this sounds reasonable. Any other suggestions?

Re: [SCM] GNU Autoconf source repository branch, master, updated. v2.67-26-gd984765

On 08/24/2010 02:13 PM, Eric Blake wrote: > Thanks. Are you planning on syncing this back to gnulib as well? No, I hadn't thought of that; thanks for reminding me. Here's what I installed: >From bde8be8f5dd1105af5fc568680df3e84a35bfec5 Mon Sep 17 00:00:00 2001 From: Paul Egger

Re: [PATCH 2/2] config.status: minimize use of $tmp

On 08/30/10 09:41, Eric Blake wrote: > - { test ! -d "${ac_tmp:=$tmp}" || rm -fr "$ac_tmp"; } && exit $exit_status > > + : "${ac_tmp:=$tmp}" > + { test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status I agree with Ralf on this point. That is, I don't know of any shells where this ch

[PATCH] docs: Posix now says "((cat))" isn't portable

4c9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2010-10-26 Paul Eggert + + docs: Posix now says "((cat))" isn't portable + * doc/autoconf.texi (Parenthesis): Update documentation to reflect + what Posix 1003.1-2008 says about "((". + 2010

Re: PATCH RFA: Add support for Go programming language

On 11/03/10 10:42, Eric Blake wrote: > Personally, I'd like GOC mnemonic of Go-compiler (to match FC for > Fortran-compiler, or CC for C compiler). I also like "GOC". (Even though it rhymes with "gawk". :-)

Re: [PATCH] Ignore boilerplate logo from MSVC on stderr.

On 11/16/2010 01:49 AM, Peter Rosin wrote: > We have a proposed patch that fixes problems. If this is talking about the patch proposed in then I'm afraid that I'll have to demur. That patch quite possibly could cause more

Re: [PATCH] Ignore boilerplate logo from MSVC on stderr.

On 11/17/2010 12:16 AM, Peter Rosin wrote: > just the other day I built a couple of > libraries with MSVC with simple > > autoreconf -i; configure CC=cl CFLAGS=-nologo [more stuff]; make > > sequences. The autoreconf step will not be needed once the libraries > in question pick up latest relea

Re: [PATCH] Ignore boilerplate logo from MSVC on stderr.

On 11/17/10 14:23, Peter Rosin wrote: > As I'm curious, would you care to elaborate on what might fail? For example, the N command might cause 'sed' to exit in some cases. Autoconf needs to be fairly conservative about unusual 'sed' commands such as 'N', as 'sed' implementations are not always bug

Re: [PATCH] Ignore boilerplate logo from MSVC on stderr.

On 11/17/10 21:47, Peter Rosin wrote: > If you take some random proprietary compiler on some > random proprietary unix, you expect autotools to cope. No, actually, I don't expect that. For example, on Solaris 10, I must pass some arguments to 'configure', or otherwise I won't be using the proprie

Re: -xc99=all and libraries on Solaris 10

library semantics, and supports C99 well enough so that Autoconf's test program passes, which is probably good enough. I pushed this into Autoconf. Comments welcome. >From 4e33814cce87f13873c7b9dd5a327fce4c98f2ca Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Mon, 27 Dec 2010 23:31

Re: Tru64 sh treats read as special builtin

On 01/16/2011 03:50 AM, Ralf Wildenhues wrote: > -@command{/bin/sh} for example). > +@command{/bin/sh} for example). Tru64/OSF 5.1 @command{sh} treats > +@command{read} as a special built-in, so it may exit if input is > +redirected from a non-existent or unreadable file. Thanks, and please apply

Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H

ing patches to autoconf and to gnulib, respectively. It implements this more-conservative suggestion. >From 81b5c5b9fafdcf0b6ba51728ff76d679d35ece13 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 4 Feb 2011 20:38:07 -0800 Subject: [PATCH] autoconf: new macro AC_HEADER_CHECK_STDBOOL * NE

Re: rebuild texinfo menus

Yes, thanks, that looks good; please install.

Re: PATCH RFA: Add support for Go programming language

On 02/13/2011 09:04 AM, Ralf Wildenhues wrote: > Any reasons against pushing this once a test with gccgo installed > passes as well? The patch looks good to me; as you say, it shouldn't break existing uses. I'd like to also hear Eric's opinion on this.

[PATCH] autoconf: tune long long tests, particularly for c99

+1,19 @@ +2011-02-16 Paul Eggert + + autoconf: tune long long tests, particularly for c99 + + This change is imported from gnulib. + * lib/autoconf/types.m4 (AC_TYPE_LONG_LONG_INT): Don't bother compiling + or running anything if c99, or if unsigned long long int doe

Re: Do not quote $SHELL when rerunning configure

On 02/26/2011 06:24 AM, Ralf Wildenhues wrote: > config.status: do not quote $SHELL when rerunning configure. Sure, that looks good; please install. Is SHELL='/bin/sh -x' documented? If not, it probably should be.

Re: docs: document several Fortran and OpenMP cache variables.

On 03/05/2011 08:35 AM, Ralf Wildenhues wrote: > The only one I think looks kinda odd in hindsight is > ac_cv_prog_c_openmp How about if we rename that to ac_cv_prog_cc_openmp, then? Might as well do it now, before it escapes.

Re: docs: BSD and Solaris make trailing space macro issue.

On 03/06/2011 04:44 AM, Ralf Wildenhues wrote: > Yes, it adds a trailing space > in the manual source. I'm not sure how useful that is, given that it > doesn't survive in the .info output. Suggestions welcome. Instead of this: # The following line contains a trailing space. foo = bar I su

[PATCH 1/3] * lib/autoconf/specific.m4 (AC_USE_SYSTEM_EXTENSIONS):, Quote cleanly.

/ChangeLog b/ChangeLog index e225350..2301762 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2011-07-22 Paul Eggert + +* lib/autoconf/specific.m4 (AC_USE_SYSTEM_EXTENSIONS): Quote cleanly. +This is imported from gnulib. gnulib also has an HP-UX 11.11 fix, but +let's s

[PATCH 2/3] * lib/autoconf/specific.m4 (AC_SYS_LARGEFILE): Port to, Mac OS X 10.5

@@ -1,3 +1,8 @@ +2011-07-30 Paul Eggert + +* lib/autoconf/specific.m4 (AC_SYS_LARGEFILE): Port to Mac OS X 10.5 +by defining _DARWIN_USE_64_BIT_INODE. Imported from gnulib. + 2011-07-22 Paul Eggert * lib/autoconf/specific.m4 (AC_USE_SYSTEM_EXTENSIONS): Quote cleanly. diff --git a

[PATCH 3/3] docs: modernize treatment of ns-resolution timestamps

hangeLog b/ChangeLog index d1b4a2f..34c5469 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2011-07-31 Paul Eggert + +docs: modernize treatment of ns-resolution timestamps +* doc/autoconf.texi (Limitations of Usual Tools): ns-resolution time +stamps are now routinely supported by

Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

The idea behind this patch sounds good to me. I haven't examined the detailed mechanics, though.

Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

On 11/08/11 03:02, Stefano Lattarini wrote: > I see that this patch might raise some questions, and some of its > effects can indeed be debatable; and anyway, it certainly leaves ample > room for improvement. Could you elaborate a bit on that? I'd rather avoid a branch if I could, and just install

Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

On 11/08/11 11:54, Stefano Lattarini wrote: >> I'd rather avoid a branch if I could, >> > > Why? That is the best way to keep the work public and going, without > risking to destabilize the code base. My experience with branches in Emacs (a much more-heavily-maintained project) is that their adv

Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

On 12/05/11 11:26, Stefano Lattarini wrote: > Ping? There is still interest in this? There's interest, yes, but alas I don't have the time to work on it. It seems you've identified four issues of which at least the first two should probably be fixed before it's shipped with autoconf. Can you co

Re: [PATCH] standards: rewrite section on quoting

This proposed patch is too strong, as it says that locale-specific quotes in English messages should use British-English style quoting (with single quotes) and it discourages American English quoting, (with double quotes). Many (perhaps most) GNU programs use American English spelling, and it'd be

Re: [PATCH] standards: rewrite section on quoting

On 12/20/11 12:11, Paolo Bonzini wrote: > single quotes are a good compromise. In the program > output, they look like the C locale alternative But that's true regardless of whether one uses single or double quotes. Either way, the program's output looks like the C locale alternative. It's more

Re: [PATCH] standards: rewrite section on quoting

On 12/21/11 03:04, Paolo Bonzini wrote: > In the C locale, GNU programs should stick to plain ASCII for quotation > -characters in messages to users: preferably 0x60 (@samp{`}) for left > -quotes and 0x27 (@samp{'}) for right quotes. It is ok, but not > -required, to use locale-specific quotes in

Re: [PATCH] standards: rewrite section on quoting

On 12/22/11 17:08, Karl Berry wrote: > +In the C locale, the output of GNU programs should stick to plain > +ASCII for quotation characters in messages to users: preferably 0x22 > +(@samp{"}) or 0x27 (@samp{'}) for both opening and closing quotes. ... > + > +That's for the output. In source files,

Re: [PATCH] standards: rewrite section on quoting

On 12/23/11 04:09, Bruno Haible wrote: > Personally I use single-quoting (apostrophes) when quoting identifiers That sounds reasonable, and is less intrusive than that what I proposed. As I understand it, the idea is to use "X" when X should be translated, and 'X' when X should not be translated.

Re: [PATCH] standards: rewrite section on quoting

On 12/23/11 15:25, Karl Berry wrote: > use "X" when X should be translated, and 'X' when X should > not be translated. > > I don't see that clearly stated in the patch. I can try to add it if > you wish (if I'm not just missing it, quite possible). Bruno thought, and I agree, that this i

Re: Solaris 10 /bin/sh, shell functions, here documents and command substitutions

On 12/24/11 07:48, Stefano Lattarini wrote: > And here is a patch to document the issue. Ok for master? Thanks, please apply.

Re: AC_PROG_LN_S limitation

On 12/26/11 00:02, Werner LEMBERG wrote: > Can this be documented, please? Or what about making AC_PROG_LN_S > work for directories also by falling back to `cp -pr'? The latter sounds better to me, though we need to use -R not -r for better portability. Thanks for reporting the problem. I pushe

Re: [PATCH] m4sh: always re-exec with $CONFIG_SHELL, if it's set

On 12/26/11 02:31, Stefano Lattarini wrote: > The three-patches series is attached. OK for master? Yes, they look good, and thanks again.

Re: AC_PROG_LN_S limitation

On 12/26/11 13:21, Stefano Lattarini wrote: >> * NEWS: >> > > Forgotten a trailing "Update" here? And ditto in the ChangeLog entry. The style I was using was: * foo: * bar (baz): log message where the log message applies to both lines. I suppose one can write it this way: * foo, bar (b

Re: [PATCH] standards: rewrite section on quoting

On 12/23/11 15:18, Paul Eggert wrote: > I'll send a gnulib patch along these lines to bug-gnulib. For convenience I broke this patch (which uses 'single quoting' when quoting code) into three parts. Part 1, like Paolo's patch, affects just the program output. It's a b

[PATCH 2/2] maint: update copyright year

@ 2012-01-03 Paul Eggert + maint: update copyright year + All files changed to add 2012, via 'make update-copyright'. + maint: resync upstream files * ChangeLog, GNUmakefile, build-aux/announce-gen: * build-aux/config.guess, build-aux/config.sub,

Re: [PATCH] Fix LEXLIB and YYTEXT_POINTER on non-ANSI systems.

On 01/04/12 00:01, Peter Rosin wrote: > Below is a patch that makes the lex library detection and >> the yytext-pointer tests not stumble when the system does >> not provide a unistd.h include. Are the tests really stumbling in that case? If 'lex' generates .c files that don't work unless one #def

Re: [PATCH] Fix LEXLIB and YYTEXT_POINTER on non-ANSI systems.

On 01/04/12 01:06, Peter Rosin wrote: > Or did you mean that configure should only #define YY_NO_UNISTD_H > when there is no unistd.h (ac_cv_header_unistd_h=no)? Yes, that's the idea, it should define YY_NO_UNISTD_H as needed. Something like the following. Does this work for you? autoconf: don'

Re: bug#10427: bug#10436: New testsuite driver and extra trailing backslash in recipes

I pushed the following doc fix into Autoconf, so that these two portability issues are documented there. It turns out that the second issue is actually due to an old Bash bug -- it's not Solaris-specific. >From b1f0e147aa7aa259dea2c34c5a0ac7965d6efd7e Mon Sep 17 00:00:00 2001 From: Pau

Re: [PATCH] getopt: fix diagnostic for missing mandatory option argument

Thanks, that patch looks good to me; please install.

Re: [PATCH] cosmetics: fix some typos in ChangeLog

On 01/15/12 10:15, Stefano Lattarini wrote: > Not sure how this is really worth, but here we go. Spelling fixes like that are always welcome.

Re: documentation of AC_FUNC_ALLOCA and mingw-w64 compilers

OK, thanks for the info. I pushed this somewhat-different fix: doc: work around mingw-w64 alloca problem with example * doc/autoconf.texi (Particular Functions): In example code for alloca, do not re-#define alloca. This works around a mingw-w64 problem reported by Vincent Torri in

Re: [PATCH] INSTALL: convert to '' quoting, drop blank line at end

That looks good to me, and thanks.

[PATCH] maint: replace FSF snail-mail addresses with URLs

* tests/erlang.at, tests/go.at, tests/statesave.m4: Replace FSF snail mail addresses with URLs, as per GNU coding standards, and for consistency with other tests. --- tests/erlang.at|4 +--- tests/go.at|4 +--- tests/statesave.m4 |4 +--- 3 files changed, 3 insertions(+), 9

[PATCH] maint: spelling fixes

I ran my little spell-checking program and pushed the following as (I hope) obvious. I took the liberty of replacing "facultative" with "optional", since I hadn't a clue what "facultative" meant until I looked it up and it does seem to be a term that's used in biology rather than in computing. --

Re: autoconf-2.68b/tests/m4sh.at

On 03/03/2012 10:32 AM, Tim Rice wrote: > -#/bin/sh > +#!/bin/sh Thanks, I pushed that fix as follows: * tests/m4sh.at (AS@&t@_EXECUTABLE): "#!/bin/sh", not "#/bin/sh". Typo reported by Tim Rice in: http://lists.gnu.org/archive/html/autoconf-patches/2012-03/msg9.html --- tests/m4sh.at |

Re: [GNU Autoconf 2.68.147-cca28] testsuite: 100 failed

Thanks, I had already found that independently, and I fixed that by pushing the following: tests: port AS_TR_SH and AS_TR_CPP test to Solaris 8 wc * tests/m4sh.at (AS@&t@_TR_SH and AS@&t@_TR_CPP): Do not assume that "wc -l" outputs only digits; on Solaris 8 it also outputs blanks and POSIX allows

[PATCH] tests: port AS_EXECUTABLE_P test to Solaris 8 /bin/sh

(I pushed this to port the new test to Solaris 8 /bin/sh.) * tests/m4sh.at (AS@&t@_EXECUTABLE): Treat any nonzero exit status as failure. This is needed for Solaris 8 /bin/sh, where executing a nonexecutable file causes the shell to say the file had exit status 1. --- tests/m4sh.at |2 +- 1

[PATCH] fortran: clean up core files after AC_FC_CHECK_BOUNDS

* lib/autoconf/fortran.m4 (AC_FC_CHECK_BOUNDS): Clean up core files, too. Needed for Sun Fortran 95 8.2 2005/10/13 on Solaris 8. --- lib/autoconf/fortran.m4 |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/lib/autoconf/fortran.m4 b/lib/autoconf/fortran.m4 index afeb3ab..

Re: [PATCH] tests: fix spurious failure due to Solaris XPG4 sh bug

On 03/04/2012 08:16 AM, Stefano Lattarini wrote: > What's going on there? That is a bug in older ksh implementations. I've pushed the following doc patch to describe it. I don't fully understand your test case, but renaming "script" to "script2" won't work if there happens to be a command named "s

[PATCH] tests: port AT_CHECK_ENV to hosts with flaky grep

* tests/local.at (AT_CHECK_ENV): Don't assume that if one grep fails, the other will too. It could be that 'grep' is flaky, and fails somewhat at random. This would explain the problems reported for autoconf-2.68b on FreeBSD and MacOS X, for example:

Re: Autoconf-2.68b possible patch for FreeBSD, MacOS X

mplains 'Regular expression too big' for a 938-byte regular expression in the test. I hope the following further patch, which is clearly needed anyway and which I just now pushed, fixes the remaining problems. >From 0f133bbea81a9e3cea1278577f498d617b89c5d8 Mon Sep 17 00:00:00 2001 From:

Re: [PATCH] remove warning for --host without --build

o be changed. >From 71d2c125cb3ad167a59776a3bab0e95169805af0 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Mon, 23 Apr 2012 10:30:05 -0700 Subject: [PATCH] doc: document --build and cross-compilation better * doc/autoconf.texi (Specifying Target Triplets): Mention that specifying a build-type that differs from host-type en

Re: [PATCH] general: deprecate 'configure.in' as autoconf input

On 05/22/2012 03:29 AM, Stefano Lattarini wrote: > +** The use of the long-deprecated name 'configure.in' for the autoconf >> + input file now elicits a warning in the 'obsolete' category. >> This change is fine with me. The only package I know that's still using configure.in is Emacs, and I c

Re: [PATCH] m4sh: avoid // issues in _AS_PATH_WALK

That patch looks good to me, and thanks.

[PATCH] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

I pushed this. I did only C11, not C++11, since I'm not a C++ guru. * NEWS: * doc/autoconf.texi (C Compiler): Document this. (Gnulib, Function Portability, Particular Functions) (Header Portability, Particular Headers, Defining Symbols) (Printing Messages, Limitations of Usual Tools) (Preprocesso

[PATCH] AC_FUNC_VFORK: check for Solaris 2.4 signal-handling bug

encouraged to define it diff --git a/lib/autoconf/functions.m4 b/lib/autoconf/functions.m4 index 5987a0c..782393b 100644 --- a/lib/autoconf/functions.m4 +++ b/lib/autoconf/functions.m4 @@ -1894,10 +1894,18 @@ AC_DEFUN([_AC_FUNC_VFORK], [AC_CACHE_CHECK(for working vfork, ac_cv_func_vfork_works, [AC_RUN

Re: [PATCH] scripts: quote `like this', not 'like this'

Thanks for doing all that. Looks good to me, not that I reviewed every line.

Re: [PATCH] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

possible mode in AC_PROG_CC makes sense. Yes, on further thought I'm inclined to agree. Also, it's a lot simpler. Also, it fixes Jim's bug. There's a lot to like. Please see the patch below, which I've pushed. Further comments welcome. >From f7fe375b26f39d0a6624a

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

e, but I just now pushed this for IBM XL C. And it will come in the other compilers. >From 97e027a8f736c9754212607cb01f87a5997699b0 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 26 Sep 2012 07:49:59 -0700 Subject: [PATCH] AC_PROG_CC: try -qlanglvl=extc1x, for IBM XL C V12.1 * lib/autoconf/c.m4 (_AC_PROG_CC_C11): Add -qlan

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

>> C11 is not incompatible with C99, the way that C99 was incompatible with C89. > > That sounds like a description why the autoconf 2.70 change of putting > the compiler into the highest possible mode in AC_PROG_CC could break > existing software? This doesn't sound likely either. There are v

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

On 09/27/2012 07:29 AM, Adrian Bunk wrote: > glibc 2.16 has the following protected by what boils down to > #if defined _GNU_SOURCE || defined _ISOC11_SOURCE || \ > (defined __STDC_VERSION__ && __STDC_VERSION__ >= 201112L) > > - timespec_get() and TIME_UTC > - aligned_alloc() > - at_quick_

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

On 09/27/2012 10:04 AM, Adrian Bunk wrote: > I merely wanted to point out that there can be a difference in what > glibc provides when we end up with gnu99 instead of gnu11. Yes. And programs using Autoconf will surely prefer the gnu11 version, which is why defaulting to gnu11 is a win. > AC_PR

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

h with IBM XL C V12.1 that you noted earlier. >From bccf4b98eebc09f4f8c77bfe4bafef41cc05e540 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 28 Sep 2012 10:44:16 -0700 Subject: [PATCH] AC_PROG_CC: clarify documentation, encourage -qlanglvl=extc1x * doc/autoconf.texi (C Compiler): Doc

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

On 10/01/2012 02:37 PM, Adrian Bunk wrote: > Now we have two compilers that will stay in C99 mode instead of C11 mode > if they are in C99 mode by default. Sorry, I don' follow. GCC and IBM XL C will both switch to C11 mode, with the current autoconf git.

Re: bug: "gcc -std=gnu99" passes AC_PROG_CC_C11

On 10/01/2012 03:20 PM, Adrian Bunk wrote: > Not if they are set to default to C99 mode. Ah. True. That may be a problem for future versions of these two compilers, though it's not a problem for current versions. To some extent, when we're talking about future software, we're at the mercy of th

Re: FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC

ch. Thanks for reporting this. The problem arises because Automake's AM_PROG_CC_C_O redefines AC_PROG_CC. We don't want to discourage people from using AC_PROG_CC, so this is an Autoconf bug. I installed this into Autoconf: >From 0cc5d3c97d4446dfb198e20f13b9850ee237ab3b Mon Sep

Re: FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC

On 10/24/2012 01:07 PM, Adrian Bunk wrote: > You also have to exclude AC_PROG_CC_C89 and AC_PROG_CC_C99 (similar > to AC_PROG_CC_STDC) in au_exclude_list in tests/mktests.sh to fix the > "make check" errors this causes. Thanks, I just now pushed a patch to do that.

Re: [PATCH 0/2] First steps in making autoconf ensure a POSIX shell

On 11/07/2012 04:37 AM, Stefano Lattarini wrote: > I want to be able to assume the make recipes > are run by a POSIX shell. Thanks. Are all the features you're testing for specified by POSIX 1003.2-1992? (That is, are they all suitably *old* POSIX?) If so, these patches look good, except that t

Re: [PATCH 0/3] Support for AC_CONFIG_MACRO_DIRS in autoconf

On 11/07/2012 12:47 AM, Stefano Lattarini wrote: > So I'll > push this series in a couple of days if there is no objection or > review by then. That sounds good to me as well. Thanks. I briefly reviewed the patch and didn't see any problems, though I didn't follow every nook and cranny.

Re: Relasing Autoconf 2.70?

On 12/19/2012 02:17 AM, Stefano Lattarini wrote: The stuff still pending about the requirement of a POSIX shell: can IMHO be delayed without problems to Autoconf 2.71 I agree. Release early and often. If we can find a

Re: alloca patch

2001 From: Paul Eggert Date: Thu, 20 Dec 2012 21:21:04 -0800 Subject: [PATCH] AC_FUNC_ALLOCA: port to recent BSDs and remove obsolete AIX * doc/autoconf.texi (Particular Functions): Remove the AIX case from the recommended code, as the most recent version of the AIX compiler that IBM still sup

Re: alloca patch

On 12/21/12 09:14, Patrick Welche wrote: > In the documentation case, if you don't HAVE_ALLOCA, why declare alloca()? The idea is that you're supplying a substitute, a la the gnulib alloca module. (If you're not, the alloca declaration shouldn't hurt anything.) > In the AC_FUNC_ALLOCA case, why

[PATCH] AC_C__GENERIC: New macro.

I needed this for an Emacs feature and it seemed like something Autoconf should have and which won't break any existing usage, so I took the liberty of pushing it. * NEWS, doc/autoconf.texi (C Compiler): Document it. * lib/autoconf/c.m4 (AC_C__GENERIC): Implement it. --- NEWS | 2 +

Re: [PATCH] AC_PROG_CC: also check whether $CC supports "-c -o" together

That looks good to me; thanks.

Re: [PATCH] m4sugar: factor away _AS_ECHO_PREPARE.

This change would break gnulib's gl_CACHE_VAL_SILENT. Is there some way you can fix that? It's OK if we have to modify gl_CACHE_VAL_SILENT, it's just that we need to modify it in a way that'll work with both old and new Autoconf. Also, any such patch to Autoconf should update the documentation a

Re: [PATCHv2] m4sugar: factor away _AS_ECHO_PREPARE.

Thanks, some minor comments: > Macros AS_ECHO and AS_ECHO_N now expand unconditionally to > + 'printf "%s\n"' and 'printf "%s"' unconditionally. They actually use single-quoted strings, so I'd change your single quotes to double and vice versa, if you want to keep the quotes (but see below). >

Re: [PATCHv3] m4sugar: factor away _AS_ECHO_PREPARE.

Thanks, that looks good to me; please push.

Re: Patch AC_USE_SYSTEM_EXTENSIONS for Minix3

Thanks, I installed the following patch, which is a bit more general as it merges recent gnulib changes in. >From 773f366de4e8db4b2b40cde047c87a175eaa20a5 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 6 Feb 2013 22:46:49 -0800 Subject: [PATCH] AC_USE_SYSTEM_EXTENSIONS: port to HP

Re: Patch AC_USE_SYSTEM_EXTENSIONS for Minix3

hout a net! But it should be harmless on non-HP-UX hosts. >From 16ce3ed2f7844356fc41f3bc4e5b7b0587fc57f7 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 8 Feb 2013 13:01:15 -0800 Subject: [PATCH] AC_USE_SYSTEM_EXTENSIONS: improve port to HP-UX * lib/autoconf/specific.m4 (AC_USE_SYSTEM_EX

Re: LIBOBJDIR documentation

p 17 00:00:00 2001 From: Paul Eggert Date: Sat, 23 Feb 2013 11:14:49 -0800 Subject: [PATCH] AC_FUNC_GETLOADAVG: doc fix * doc/autoconf.texi (Particular Functions): Omit incorrect mention of @var{dir} before getloadavg.c. Problem reported by Patricke Welche in: http://lists.gnu.org/archive/html/autoco

Re: extra error messages on Mac OS X

Thanks, I pushed the following slightly-different patch (I found a couple more instances of the problem): >From e14f3fe48c2b206d3ec4e0afaa4c7b2c99349b4a Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 8 Mar 2013 08:56:18 -0800 Subject: [PATCH] AC_PROG_CC etc: avoid warnings when remov

[PATCH] AC_PROG_CC etc: avoid warnings when removing conftest* on OS X

I forgot one of the fixes Mr. Nakada reported for the 2013-03-08 fix. * lib/autoconf/general.m4 (AC_EGREP_CPP): Use rm -rf, not just rm -f, when removing conftest*. --- lib/autoconf/general.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/autoconf/general.m4 b/lib/autocon

Re: AC_PROG_YACC: use bison -o y.tab.c

Thanks, I installed that into Autoconf with a slightly terser NEWS entry: - AC_PROG_YACC now uses 'bison -o y.tab.c' instead of 'bison -y', so that by default it no longer warns about Bison extensions. Add -Wyacc to YFLAGS to enable these warnings.

Re: [RFC] Convert the Autoconf build system to non-recursive make

On 05/05/2013 02:28 PM, Stefano Lattarini wrote: > If there is any interest in integrating this, I will write proper > commit messages (in GNU ChangeLog style) for all the patches. Thanks, it looks good to me.

Re: [PATCH v2 00/17] Convert the autoconf build system to non-recursive make

On 05/06/13 06:20, Stefano Lattarini wrote: > The series should be > good to apply, albeit more testing (especially on systems != GNU/Linux) > would be highly appreciated. Thanks, looks good. I'd just apply it. The autoconf tests right now have a lot of problems on non-GNU/Linux hosts. I don't t

Re: [PATCH] maint: sync several files from upstream

Thanks, looks good. This sort of thing should be routine.

Re: [PATCH] Add missing comma to AC_FUNC_VPRINTF (fwd)

Thanks, I pushed that into the autoconf master.

[PATCH] doc: don't push 'static inline'

* doc/autoconf.texi (Function Portability): Use plain 'static', not 'static inline', in example. These days, 'static' is enough; optimizing compilers can figure out the 'inline' on their own. --- doc/autoconf.texi | 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git

Re: [PATCH 0/3] Modernize header checks, v2

Zack Weinberg wrote: > One remaining wart is that autoupdate > replaces AC_HEADER_STDC with an overt invocation of > _AC_INCLUDES_DEFAULT_REQUIREMENTS. I couldn't find an AU_DEFUN > construct that didn't expose this internal macro but would still DTRT > both before and after an autoupdate run. Id

  1   2   3   4   5   6   7   8   9   10   >