Re: [PATCH] docs: more details about make VPATH rewriting woes

* Stefano Lattarini wrote on Thu, Sep 15, 2011 at 11:21:16AM CEST: > On Thursday 15 September 2011, Ralf Wildenhues wrote: > > * Stefano Lattarini wrote on Wed, Sep 14, 2011 at 11:35:37AM CEST: > > > On Wednesday 14 September 2011, Ralf Wildenhues wrote: > > > >

Re: [PATCH] docs: more details about make VPATH rewriting woes

* Stefano Lattarini wrote on Wed, Sep 14, 2011 at 11:35:37AM CEST: > On Wednesday 14 September 2011, Ralf Wildenhues wrote: > > It applies to any word that is surrounded by whitespace (or beginning or > > end of command line), regardless of shell syntax. Please don't > >

Re: [PATCH] docs: more details about make VPATH rewriting woes

Hi Stefano, * Stefano Lattarini wrote on Tue, Sep 13, 2011 at 03:15:04PM CEST: > * doc/autoconf.texi (Automatic Rule Rewriting): Solaris make > VPATH rewriting might apply also to shell variables, functions > and keywords (and automake has already tripped on this once); > document this, with an ex

New macro AC_FC_PP_DEFINE for the preprocessor define flag.

The infrastructure for handling preprocessed Fortran better is still lacking quite a bit; e.g., it would be nice to generate lazily-updated config headers with Fortran-style comments. For now, I use this as a workaround in projects: AC_CONFIG_HEADERS([config.h]) # Convert config.h into an fco

Re: New macro AC_FC_PP_SRCEXT for preprocessed file extensions.

* Ralf Wildenhues wrote on Sat, Mar 05, 2011 at 07:59:27PM CET: > I haven't pushed this patch yet; I'd really appreciate some comments. No comments, I've pushed this patch now, with minor testsuite fixes as below folded in. Thanks, Ralf > New macro AC_FC_PP_SRCEXT

[PATCH 3/2] New macro AC_FC_MODULE_OUTPUT_FLAG: module output directory.

.m4 | 62 +++ tests/local.at |2 +- 5 files changed, 103 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index bdbce27..2ac8acf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,12 @@ +2011-04-02 Ralf Wildenhues + +

Re: [PATCH 0/2] Fortran 90 module file extension and include path

Hello, and sorry for the delay, * Julian Cummings wrote on Thu, Mar 10, 2011 at 02:01:41AM CET: > > My first question would be how to properly credit the original authors > > of these macros. Luc, Julian, Alexander, I'd be glad to list y'all as > > authors and add you to the Autoconf THANKS fil

Re: [PATCH 2/2] New macro AC_FC_MODULE_FLAG: Fortran 90 module include path.

* Ralf Wildenhues wrote on Sun, Mar 06, 2011 at 01:54:07PM CET: > * lib/autoconf/fortran.m4 (AC_FC_MODULE_FLAG): New macro, > adjusted and rewritten from the AX_F90_MODULE_FLAG macro from > the Autoconf Macro Archive by Luc Maisonobe, Julian C. Cummings, > and Alexander Plet

Re: [PATCH] README-hacking: fix typo

Hi Jim, * Jim Meyering wrote on Sat, Mar 26, 2011 at 09:51:15PM CET: > Here's a tiny fix: > Subject: [PATCH] README-hacking: fix typo > > * README-hacking: s/just build/just built/. Pushed, thanks! Cheers, Ralf

Re: [PATCH] AC_INIT: properly quote package name containing m4 macro

Hi Eric, * Eric Blake wrote on Thu, Mar 17, 2011 at 05:57:48PM CET: > We have an existing use case that argues for unexpanded (automake's > desire to write tests for dummy packages that use arbitrary names that > happen to match m4 builtins that aren't in the m4_ reserved namespace). Automake wou

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

* Paul Eggert wrote on Sun, Mar 06, 2011 at 06:33:36PM CET: > Instead of this: > > # The following line contains a trailing space. > foo = bar > > I suggest this: > > foo = bar # Note the space after "bar". Sounds good. Thanks! Ralf

[PATCH 2/2] New macro AC_FC_MODULE_FLAG: Fortran 90 module include path.

<...> + Julian C. Cummings <...> + Alexander Pletzer <...> + Ralf Wildenhues <...> + + New macro AC_FC_MODULE_FLAG: Fortran 90 module include path. + * lib/autoconf/fortran.m4 (AC_FC_MODULE_FLAG): New macro, + adjuste

[PATCH 1/2] New macro AC_FC_MODULE_EXTENSION: Fortran 90 module extension.

(-) diff --git a/ChangeLog b/ChangeLog index ed4c467..9570ce7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,16 @@ +2011-03-06 Luc Maisonobe <...> + Alexander Pletzer <...> + Ralf Wildenhues <...> + + New macro AC_FC_MODULE_EXTENSION: Fortran 9

[PATCH 0/2] Fortran 90 module file extension and include path

Hello everyone, I would like to see improved Fortran support in Autotools, and for eventual dependency tracking in Automake (and other purposes) we need to know the name of module files and how to modify the include path. Now, the AX_F90_MODULE_EXTENSION and AX_F90_MODULE_FLAG macros from the Aut

docs: BSD and Solaris make trailing space macro issue.

OK to push? This prepares the next couple of patches. 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. Thanks, Ralf docs: BSD and Solaris make trailing space macro issue. *

New macro AC_FC_PP_SRCEXT for preprocessed file extensions.

Fortran and preprocessing is another long story, not even starting with COCO. Of those Fortran 90+ compilers that I can get hold of, all provide some way or another to enable preprocessing of source files with all kinds of file name extensions. It just isn't easy sometimes (esp. older gfortran to

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

Hello Paul, * Paul Eggert wrote on Sat, Mar 05, 2011 at 06:13:54PM CET: > 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? >

Re: New macro AC_FC_IMPLICIT_NONE to disable Fortran implicit int.

* Ralf Wildenhues wrote on Sat, Mar 05, 2011 at 09:37:55AM CET: > New macros AC_{F77,FC}_IMPLICIT_NONE to disable Fortran implicit int. > > * lib/autoconf/fortran.m4 (_AC_FC_IMPLICIT_NONE): New internal > macro. > (AC_F77_IMPLICIT_NONE, AC_FC_IMPLICIT_NO

docs: document several Fortran and OpenMP cache variables.

I went ahead and documented a bunch of cache variables, as below. The only one I think looks kinda odd in hindsight is ac_cv_prog_c_openmp, as all other ac_cv_prog_* cache variables that deal with the C compiler use cc not c as key. Thanks, Ralf docs: document several Fortran and OpenMP cach

Re: New macro AC_FC_IMPLICIT_NONE to disable Fortran implicit int.

* Ralf Wildenhues wrote on Sat, Mar 05, 2011 at 09:37:55AM CET: > New macros AC_{F77,FC}_IMPLICIT_NONE to disable Fortran implicit int. > > * lib/autoconf/fortran.m4 (_AC_FC_IMPLICIT_NONE): New internal > macro. > (AC_F77_IMPLICIT_NONE, AC_FC_IMPLICIT_NO

AC_FC_SRCEXT: allow gfortran to compile .f77 files.

While the .f77 extension is not supported by all Fortran compilers, it is documented by some, we already test it in the "AC_FC_SRCEXT usage" test, and when we can get more compilers to accept it, that can only be helpful. I'm pushing the patch below to get gfortran to accept this extension. Thank

Re: New macro AC_FC_IMPLICIT_NONE to disable Fortran implicit int.

* Eric Blake wrote on Tue, Mar 01, 2011 at 08:54:50PM CET: > On 02/27/2011 09:18 AM, Ralf Wildenhues wrote: > > Another fairly simple Fortran macro, with data gathered from manuals > > and from the overview site which Eve-Marie linked to. > Same comments as the las

Re: AC_FC_CHECK_BOUNDS for Fortran array bounds checking.

* Eric Blake wrote on Tue, Mar 01, 2011 at 08:53:02PM CET: > On 02/27/2011 09:10 AM, Ralf Wildenhues wrote: > > > > here's a first macro to improve Fortran support in Autoconf. > > It uses Fortran 90 interface declarations, so a F77 version > > would have to be d

Re: Exclude M4 with buggy strstr when configuring Autoconf.

* Eric Blake wrote on Mon, Feb 28, 2011 at 07:06:50PM CET: > On 02/26/2011 07:50 AM, Ralf Wildenhues wrote: > >> Autoconf's m4/m4.m4 needs a similar test. > > > > Thanks. Like this? > > Close, but I'm still thinking about it. > > There's t

Re: [PATCH] Document AC_FUNC_FORK cache variables

Hello Eric, in http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/7500/focus=7501 I asked the following: * Ralf Wildenhues wrote on Mon, Dec 20, 2010 at 07:57:11AM CET: > * Colin Watson wrote on Mon, Dec 20, 2010 at 12:33:46AM CET: > > I maintain a package where I'd l

Update known compiler switches for Fortran and OpenMP macros.

This patch is my current known set of updates for existing Fortran macros. Most of the switches are taken from manuals only (I don't really have access to that many compilers), so there might still be bugs. I plan to ask a couple of people with other Fortran compilers once my patch queue is fairl

docs: macro synopses document default failure cases. (was: AC_FC_CHECK_BOUNDS for Fortran array bounds checking.)

* Eric Blake wrote on Tue, Mar 01, 2011 at 08:53:02PM CET: > On 02/27/2011 09:10 AM, Ralf Wildenhues wrote: > > here's a first macro to improve Fortran support in Autoconf. > > OK to push? Eve-Marie, OK to add your name and email to THANKS? > > OK from my end, after

Re: fort77(f2c wrapper) is not properly detected

* Giulio Paci wrote on Tue, Dec 07, 2010 at 01:43:15AM CET: > Il 05/12/2010 22:19, Ralf Wildenhues ha scritto: > Output changes from: > > Fortran low level compiling/preprocessing macros. > > 303: GNU Fortran 77 FAILED (fortran.at:31)

Re: New macro AC_FC_FPE_TRAP for Fortran FP Exception handling.

* Ralf Wildenhues wrote on Sun, Feb 27, 2011 at 05:37:27PM CET: > This patch is still in somewhat of an alpha stage. The new macro is > probably overly complex (and I'm not sure whether it's best to handle > the first argument at configure time, or earlier at autoconf time in

Re: Update documentation for AC_FC_LINE_LENGTH compiler switches.

* Ralf Wildenhues wrote on Sun, Feb 27, 2011 at 05:27:42PM CET: > I'll push this along the other commits once approved. > (Rebasing and reordering the patches is a bit awkward, > as the patches introducing new macros all append to the > same file.) Never mind, I meant to merge an

New macro AC_FC_FPE_TRAP for Fortran FP Exception handling.

This patch is still in somewhat of an alpha stage. The new macro is probably overly complex (and I'm not sure whether it's best to handle the first argument at configure time, or earlier at autoconf time in m4), and the test is too strict so that it fails on most systems. The latter has two reaso

Update documentation for AC_FC_LINE_LENGTH compiler switches.

I'll push this along the other commits once approved. (Rebasing and reordering the patches is a bit awkward, as the patches introducing new macros all append to the same file.) Thanks, Ralf Update documentation for AC_FC_LINE_LENGTH compiler switches. * lib/autoconf/fortran.m4 (AC_FC

Reword Fortran macro documentation.

The formulation was a bit awkward to read, this should help it. OK? Thanks, Ralf Reword Fortran macro documentation. * doc/autoconf.texi (Fortran Compiler): Improve wording for AC_FC_FREEFORM, AC_FC_FIXEDFORM, and AC_FC_LINE_LENGTH macros. diff --git a/doc/autoconf.texi b/doc/a

New macro AC_FC_IMPLICIT_NONE to disable Fortran implicit int.

Another fairly simple Fortran macro, with data gathered from manuals and from the overview site which Eve-Marie linked to. No test so far except for the automatic self-test created by mktests.sh. OK to push? Thanks, Ralf New macro AC_FC_IMPLICIT_NONE to disable Fortran implicit int.

AC_FC_CHECK_BOUNDS for Fortran array bounds checking. (was: flags for different fortran compilers)

[ moving from autoconf@ to -patches@ ] Hello, here's a first macro to improve Fortran support in Autoconf. It uses Fortran 90 interface declarations, so a F77 version would have to be different (and I'm not quite sure whether this works as well in Fortran 77). I only have access to a few of the

Exclude M4 with buggy strstr when configuring Autoconf. (was: configure oddity)

a buggy m4 that the user has explicitly set by setting the M4 environment variable. It seems like a bug in AC_MSG_ERROR that I cannot use a comma in the message, with the current amount of quoting. Thanks, Ralf 2011-02-26 Ralf Wildenhues Eric Blake Exclude M4 wit

Do not quote $SHELL when rerunning configure

Hello Paul, all, in commit 1be64afa5b45bf6cd82a0d118d8442527d9296fe, you quoted '$SHELL' in the code below. That strikes me as weird, because it prevents me from doing funky debugging like this: CONFIG_SHELL='/bin/sh -x' /bin/sh -x ./configure ./config.status --recheck # I'd like

Re: bug#8111: after adding a(nother) subconfigure, rerunning make fails

[ dropping bug-automake ] * Jack Kelly wrote on Fri, Feb 25, 2011 at 10:38:39PM CET: > On Sat, Feb 26, 2011 at 7:46 AM, Ralf Wildenhues wrote: > > [ adding autoconf-patches; this is <http://debbugs.gnu.org/8111> ] > > * Jack Kelly wrote on Thu, Feb 24, 2011 at 11:49:44PM CET

Re: bug#8111: after adding a(nother) subconfigure, rerunning make fails

[ adding autoconf-patches; this is <http://debbugs.gnu.org/8111> ] * Jack Kelly wrote on Thu, Feb 24, 2011 at 11:49:44PM CET: > On Fri, Feb 25, 2011 at 6:36 AM, Ralf Wildenhues wrote: > > Can we fix this somehow in either Autoconf or Automake? > > Could we save t

Re: PATCH RFA: Add support for Go programming language

Hi Eric, * Eric Blake wrote on Mon, Feb 21, 2011 at 03:06:17PM CET: > On 02/20/2011 10:35 AM, Ralf Wildenhues wrote: > > Thanks. Eric, would you mind if I went ahead with this patch? > > Sorry for my long silence on the matter. No worries. > > I'm fully aware that

Re: AC_OPENMP broken for IBM xl Fortran compilers

[ dropping autoconf@, adding bug-gnulib@ ] * Christian Rössel wrote on Sun, Feb 20, 2011 at 11:06:40AM CET: > Am 2/20/2011 7:55 AM, schrieb Ralf Wildenhues: > > * Christian Rössel wrote on Fri, Feb 18, 2011 at 03:57:30PM CET: > >> AC_OPENMP returns "none needed" for

Re: PATCH RFA: Add support for Go programming language

Hello, * Paul Eggert wrote on Sun, Feb 13, 2011 at 09:35:31PM CET: > 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

Re: AC_OPENMP broken for IBM xl Fortran compilers

Hi Christian, Markus, * Christian Rössel wrote on Fri, Feb 18, 2011 at 03:57:30PM CET: > AC_OPENMP returns "none needed" for the IBM xl Fortran compilers (xlf*, > bgxlf*, mpixlf*). This is wrong, you need to use -qsmp=omp. > > configure tries to compile following program: > > | program mai

Re: configure -C by default?

[ moving from autoconf@ to -patches ] * Brian Gough wrote on Mon, Feb 07, 2011 at 01:45:04PM CET: > Maybe it would help to publicise "-C" in the output so people > are more aware of it. e.g. > > $ ./configure > configure: not caching test results (use -C to enable) > checking for a

Re: PATCH RFA: Add support for Go programming language

* Ralf Wildenhues wrote on Mon, Dec 20, 2010 at 08:15:29AM CET: > * Eric Blake wrote on Wed, Nov 03, 2010 at 06:42:54PM CET: > > On 11/03/2010 11:38 AM, Ian Lance Taylor wrote: > > >> It otherwise seems low-danger to me, but > > >> I wouldn't want to mo

Re: fort77(f2c wrapper) is not properly detected

ding by '.c' or '.c"', that is where TMPDIR > > appears) even if fort77 get fixed. However I am not able to test it. > > > Any news? Thanks for the updated patch. I took it and made the sed script portable, added you to THANKS, and committed as below after

rebuild texinfo menus

OK? Thanks, Ralf 2011-02-06 Ralf Wildenhues * doc/autoconf.texi: Rebuild menus using emacs ^C ^U ^A. diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 1fbb7ad..232ed81 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -340,7 +340,7 @@ Top * Preset Output Variables

Re: parallel make and I/O of child processes

* Stefano Lattarini wrote on Tue, Jan 25, 2011 at 11:02:11AM CET: > So, what about the attached updated patch? I have some nits, otherwise I'll let Eric approve this. > Subject: [PATCH] docs: another parallel make issue > > * doc/autoconf.texi (Parallel Make): Document that some make > implement

Re: HP-UX make causes autoconf timestamp issues

* Eric Blake wrote on Mon, Jan 24, 2011 at 10:10:53PM CET: > On 01/24/2011 02:00 PM, Ralf Wildenhues wrote: > >> That is, is it only an autoconf bug, > >> where if you fix the autoconf bug, then all other victims will be fixed? > > > > No. If you are buildin

Re: parallel make and I/O of child processes

* Stefano Lattarini wrote on Mon, Jan 24, 2011 at 11:38:28PM CET: > Subject: [PATCH] docs: another parallel make issue > > * doc/autoconf.texi (Parallel Make): Document that some make > implementations, when run in parallel mode, connect stdout and > stderr of child processes to pipes or temporary

Re: Fix remake rule-induced test failures with HP-UX make.

* Ralf Wildenhues wrote on Sat, Jan 15, 2011 at 01:55:18PM CET: > > http://autobuild.josefsson.org/automake/log-201101150749395803000.txt > docs: HP-UX make remakes targets with same time stamps as prereqs > > * doc/autoconf.texi (Timestamps and Make): Document HP-UX 1

Re: HP-UX make causes autoconf timestamp issues

Hi Eric, thanks for the reviews! * Eric Blake wrote on Mon, Jan 24, 2011 at 05:14:49PM CET: > On 01/23/2011 03:56 AM, Ralf Wildenhues wrote: > > all due to the bug that HP-UX make considers targets out of date when > > they have the same time stamp as a prerequisi

HP-UX make causes autoconf timestamp issues

http://autobuild.josefsson.org/automake/log-201101181921247117000.txt This HP-UX 11.31 system is fast enough to trigger test failures for at least these Automake tests, besides the ones already fixed: insthook libobj16b output10 posixsubst-data posixsubst-scripts subcond2 subpkg2 suffix13 all due

whitespace and macros from the command line

Another patch set to document make limitations in autoconf.texi, and fix the respective test failures in Automake. I have a separate patch for Automake maint I'd like to apply, since this is such a long-standing failure. I'm not actually sure if Posix mandates the stripping of leading whitespace

Re: trailing whitespace in make macros

* Eric Blake wrote on Sat, Jan 22, 2011 at 03:03:02PM CET: > Should we also mention the converse issue of non-comments? That is, > Posix requires that # embedded in the middle of a rule (and not a macro) > is okay. Which is why gnulib's include-next module works [...] Yes, sure. There already e

Re: avoid buggy AIX 5.3 cp -R.

Hi Eric, * Eric Blake wrote on Sat, Jan 22, 2011 at 02:46:29PM CET: > On 01/22/2011 05:45 AM, Ralf Wildenhues wrote: > > automake/tests/fn99{,subdir}.test have been long-time failures on > > AIX 5.[123], but not 6.1 or newer (and IIRC not 4.3.3 either): > > http://autobuild.j

avoid buggy AIX 5.3 cp -R.

automake/tests/fn99{,subdir}.test have been long-time failures on AIX 5.[123], but not 6.1 or newer (and IIRC not 4.3.3 either): http://autobuild.josefsson.org/automake/log-201101181921915482000.txt | + make distcheck | make dist-gzip am__post_remove_distdir='@:' | { test ! -d "fn

Re: trailing whitespace in make macros

* Stefano Lattarini wrote on Sat, Jan 22, 2011 at 12:14:27PM CET: > On Saturday 22 January 2011, Ralf Wildenhues wrote: > > docs: new sections about macros and comments, substitutions. > > > Why the comma after "comments"? Has the sentence got borked somehow? It

trailing whitespace in make macros (was: bug#7868: splitting up test suites)

[ moving from automake bug#7868 ] * Ralf Wildenhues wrote on Sat, Jan 22, 2011 at 11:06:48AM CET: > * Stefano Lattarini wrote on Thu, Jan 20, 2011 at 10:19:24PM CET: > > On Thursday 20 January 2011, Ralf Wildenhues wrote: > > > That is the reason the check-TESTS rule is so ugly

Fix LEXLIB and YYTEXT_POINTER with IRIX 6.5 flex 2.5.4.

http://autobuild.josefsson.org/automake/log-201101181921817456000.txt On IRIX, the code from AC_PROG_LEX sees something like this: $ cc -o conf lex.yy.c -ll cc-1042 cc: ERROR File = conf.l, Line = 6 The types of operands "char *" and "int" are incompatible. { yyless (input () != 0); } ^

Tru64 sh treats read as special builtin

First off, please consider this squashed in with my previous patch: @@ -20184,7 +20186,7 @@ Timestamps and Make @end example Apart from timestamp resolution, there are also differences in handling -equal timestamps. HP-UX @command{make} updates targets if it has the +equal timestamps. HP-UX

Re: Fix remake rule-induced test failures with HP-UX make.

[ adding autoconf-patches ] * Ralf Wildenhues wrote on Sat, Jan 15, 2011 at 11:31:55AM CET: > Quoting parts of: > http://autobuild.josefsson.org/automake/log-201101150749395803000.txt > I'm not quite sure why HP-UX make seems to trigger rebuild rules for > prerequisites that ha

Re: configmake doc?

* Karl Berry wrote on Mon, Jan 10, 2011 at 01:36:51AM CET: > (Eric/Ralf, you can add a specific reference to the new "configmake" > node from the Automake/Autoconf manuals now if you wish.) Done. Thanks, Ralf docs: link to Gnulib configmake documentation. * doc/autoconf.texi (Defini

Re: [FYI] docs: cygnus mode doesn't require AM_CYGWIN32 macro.

[ dropping bug-autoconf ] * Ralf Wildenhues wrote on Sun, Jan 09, 2011 at 10:19:56AM CET: > * Ralf Wildenhues wrote on Wed, Dec 22, 2010 at 07:22:24AM CET: > > Hmpf. Nowadays AM_CYGWIN just expands to AC_CYGWIN, which causes > > $CYGWIN to be set. The latter is probably a bad

Re: [FYI] docs: cygnus mode doesn't require AM_CYGWIN32 macro.

[ replacing automake-patches with autoconf-patches ] tying up another loose end: * Ralf Wildenhues wrote on Wed, Dec 22, 2010 at 07:22:24AM CET: > Hmpf. Nowadays AM_CYGWIN just expands to AC_CYGWIN, which causes > $CYGWIN to be set. The latter is probably a bad idea for other reasons >

Re: [PATCH] {master} Tests: normalize use of the 'errexit' shell flag.

* Eric Blake wrote on Sat, Jan 08, 2011 at 10:40:11PM CET: > > If we can find and correct it; I suggest the first patch below, > > otherwise the second. OK to push? > Let's go with a third option - start with the second, > > > docs: link to 'set -e' shell behavior overview. > > > >

Re: [PATCH] {master} Tests: normalize use of the 'errexit' shell flag.

[ adding -patches ] * Eric Blake wrote on Mon, Jan 03, 2011 at 10:22:32PM CET: > [redirecting to bug-autoconf] > > On 01/03/2011 02:17 PM, Ralf Wildenhues wrote: > > These two were added by me in fear of shells resetting errexit upon > > function entry (like some shells

Re: bug#7773: (lack of) config.h description in manual

[ adding autoconf-patches, dropping the Automake bug ] * Eric Blake wrote on Tue, Jan 04, 2011 at 01:33:42AM CET: > I also agree that the autoconf manual should mention the gnulib > 'configmake' module (it doesn't, yet). Proposed patch. OK to push? I didn't find a place in the gnulib manual whe

Re: [PATCH 1/2] maint: new rule to update copyright year ranges

Hi Karl, * Karl Berry wrote on Mon, Jan 03, 2011 at 12:58:23AM CET: > > And, does anyone mind if I remove the @acronym commands from > > install.texi, per our too-long prior discussion? > > FWIW, I don't mind, but please do it in upstream Autoconf. > > I don't currently have write pe

Re: PATCH RFA: Add support for Go programming language

* Eric Blake wrote on Wed, Nov 03, 2010 at 06:42:54PM CET: > On 11/03/2010 11:38 AM, Ian Lance Taylor wrote: > >> It otherwise seems low-danger to me, but > >> I wouldn't want to move forward on the Libtool sister patch without this > >> one cleared. > > > > I'm at the point with my gcc patches w

Re: [PATCH] Document AC_FUNC_FORK cache variables

t;In order to override the test, you also need to set the @code{ac_cv_func_fork} and @code{ac_cv_func_vfork} variables." Eric? Thanks, Ralf 2010-12-20 Ralf Wildenhues Fix AC_FUNC_FORK to not override pre-set cache variables. * lib/autoconf/functions.m4 (AC_FUNC_FORK): Do not

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

Hello Peter, * Peter Rosin wrote on Thu, Nov 18, 2010 at 11:15:21PM CET: > > This difference in mindset when trying to build a package is > what I'm getting at, as I think people will give up more quickly > when they attempt a MSVC build, as it surely can't just work... I'm sorry this is draggin

stable branch (was: PATCH RFA: Add support for Go programming language)

* Eric Blake wrote on Wed, Nov 03, 2010 at 06:42:54PM CET: > Sorry, I've been swamped by some other tasks lately, and have not looked > at this patch yet. I also need to make good on my promise to split off > a stable branch and 2.68.1 release, while applying feature patches like > Go support onto

Re: PATCH RFA: Add support for Go programming language

Hello Eric, Ian, * Ian Lance Taylor wrote on Tue, Oct 12, 2010 at 11:06:07PM CEST: > Ralf Wildenhues writes: > > >> +...@defmac AC_PROG_GO (@ovar{compiler-search-list}) > >> +Find the Go compiler to use. Check whether the environment variable > >> +...@code{gccg

Re: Overriding LN_S

By the way, you can test the new tests with make check TESTSUITEFLAGS='-v -d -x -k AS_LN_S -k AC_PROG_LN_S' * Ralf Wildenhues wrote on Sat, Oct 16, 2010 at 11:30:01AM CEST: > --- a/tests/m4sh.at > +++ b/tests/m4sh.at > @@ -518,6 +518,32 @@ AT_CHECK([$CONFIG_SHELL ./scr

Re: Overriding LN_S

Here's testsuite exposure for your patch. - AS_LN_S is undocumented at the moment. This would be a good opportunity to document it, OTOH there is no pressing need, testsuite coverage for undocumented APIs is not a problem. - Your patch doesn't work: specifying LN_S as argument on the configure c

Re: Overriding LN_S

* Peter Rosin wrote on Fri, Oct 15, 2010 at 11:15:33PM CEST: > Den 2010-10-15 19:51 skrev Ralf Wildenhues: > > With that fixed, I ran the testsuite on GNU/Linux once without LN_S set, > > once with export LN_S='cp -p', both successfully, but with LN_S=bla, the >

Re: Overriding LN_S

Hi Peter, * Peter Rosin wrote on Fri, Oct 15, 2010 at 09:28:53AM CEST: > I haven't actually tested the patch, but it seems trivial enough. Bzzt. You are just barely saved yourself by admitting it upfront! ;-> > --- a/lib/m4sugar/m4sh.m4 > +++ b/lib/m4sugar/m4sh.m4 > else > - as_ln_s='cp -p'

Re: PATCH RFA: Add support for Go programming language

Hi Ian, * Ian Lance Taylor wrote on Tue, Oct 12, 2010 at 09:37:40PM CEST: > This patch adds support for the Go programming language to autoconf. > The Go programming language is described at http://golang.org/ . > > This is fairly basic support. It only works with gccgo, the Go frontend > to gcc

tests: avoid AC_CACHE_CHECK test failure with dash.

dash immediately exits a script with status 2 when a source'd '.' file has a syntax error, and doesn't return to the sourcing script. That's fine as per Posix, I guess, so normalize the exit status in the test, and if we don't find the error message, at least ensure the script didn't configure. OK

AT_CHECK_PROGRESS

Hello people interested in Autotest progress, a while ago, we already pondered a bit: http://thread.gmane.org/gmane.comp.sysutils.autoconf.bugs/5408 about what I called AT_CHECK_INTERACTIVE back then, namely an AT_CHECK variant that would print output already while the commands were running, mostl

Re: Documentation correction

Josh replied off-list to my mail on the autoconf list, I'm pushing this patch in his name and adding him to THANKS. The (tiny change) annotation denotes that no copyright papers have been exchanged. Cheers, Ralf 2010-09-24 Joshua G. Hale(tiny change) docs: fix typo in AC_CONFIG_FIL

Re: [PATCH 1/2] AC_REPLACE_FUNCS: restore shell loop for non-literal

Hi Eric, * Eric Blake wrote on Wed, Sep 22, 2010 at 01:14:09AM CEST: > * lib/autoconf/functions.m4 (AC_REPLACE_FUNCS): Handle > non-literals, which was lost in 2010-02-26 optimization. > * tests/semantics.at (AC_REPLACE_FUNCS): Enhance test. > * NEWS: Document the fix. > * THANKS: Update. > Report

[PATCH] Add autom4te traces for likely future Automake macros.

* lib/autom4te.in (Automake-preselections): Trace AM_MAKEFILE_INCLUDE, AM_NLS, AM_POT_TOOLS, AM_PATH_GUILE, AM_PROG_MOC, AM_XGETTEXT_OPTION, _AM_MAKEFILE_INCLUDE. Signed-off-by: Ralf Wildenhues --- * Ralf Wildenhues wrote on Sat, Sep 18, 2010 at 07:23:54AM CEST: > I've considered addi

remaining patches (was: [PATCH] build: support autobuild)

* Eric Blake wrote on Sat, Sep 18, 2010 at 01:05:50AM CEST: > Any other last-minute patches to include before I start the release > process? Right now, it looks like I will have things out the door > on Monday. All stuff that I have is either not ready for prime time yet (sorry Peter) or can wait

Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

* Eric Blake wrote on Thu, Sep 16, 2010 at 08:00:54PM CEST: > On 09/16/2010 11:56 AM, Ralf Wildenhues wrote: > >More generally, it either also requires that we bump Automake's version > >requirement on Autoconf, or we make the "autom4te preselections" test in >

Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

[ adding autoconf-patches ] * Peter Rosin wrote on Thu, Sep 16, 2010 at 10:50:05AM CEST: > --- a/automake.in > +++ b/automake.in > @@ -5242,6 +5262,7 @@ sub scan_autoconf_traces ($) > AM_GNU_GETTEXT_INTL_SUBDIR => 0, > AM_INIT_AUTOMAKE => 0, > AM_MAINTAIN

autobuild logs for Autoconf

Hi Eric, I sent a bunch of logs to http://autobuild.josefsson.org/autoconf/ for git Autoconf plus the two diffs below. The second is for Solaris 2.6 whose compiler generates core files for one particular configure test (don't remember which) which causes lots of spurious test failures. In my tes

Re: docs: document zsh specialty with empty here-documents.

Hi Gary and Eric, * Eric Blake wrote on Mon, Sep 13, 2010 at 04:40:06PM CEST: > On 09/12/2010 09:55 PM, Gary V. Vaughan wrote: > >On 12 Sep 2010, at 23:41, Ralf Wildenhues wrote: > >>docs: document zsh specialty with empty here-documents. > >> > >>* doc

docs: document zsh specialty with empty here-documents.

OK? The AT_DATA documentation already specifies that $2 should end in a newlines, so that part didn't need an update. Thanks, Ralf docs: document zsh specialty with empty here-documents. * doc/autoconf.texi (Here-Docume

docs: document zsh special array $options.

Quoting zshall(1): THE ZSH/PARAMETER MODULE The zsh/parameter module gives access to some of the internal hash tables used by the shell by defining some special parameters. options The keys for

doc: minor updates.

OK? This makes all @uref's look nice in PDF output. Thanks, Ralf doc: minor updates. * doc/autoconf.texi (Generic Compiler Characteristics): Use second argument of @uref consistently, for nicer OpenMP link. (Polymorphic Variables): Restore font-lock. (Debugging): Add ite

Re: [PATCH 2/2] doc: index entries for non-environment, non-output variables.

Hi Eric, and thanks for the reviews, I've taken the uncontroversial part of 1/2 and pushed that now. * Eric Blake wrote on Tue, Sep 07, 2010 at 04:29:51PM CEST: > On 09/06/2010 12:06 AM, Ralf Wildenhues wrote: > >@@ -4316,6 +4316,7 @@ Generic Programs > >@ovar{action-

Re: [PATCH] docs: mention traditional awk limitation

* Eric Blake wrote on Tue, Sep 07, 2010 at 11:53:10PM CEST: > * doc/autoconf.texi (Limitations of Usual Tools) : Mention > that traditional awk lacks ENVIRON. > Reported by Ralf Wildenhues. > Does this patch look okay? Yep, thanks! The Solaris awk(1) page is really succinct, the onl

Document and test AT_CHECK args shell execution environment. (was: document $at_status for use in RUN-IF-{PASS,FAIL} of AT_CHECK)

* Ralf Wildenhues wrote on Mon, Sep 06, 2010 at 08:08:55AM CEST: > autotest: document and test at_status semantics. And while we are here, we could also document the execution environment of the first, fifth, and sixth argument for AT_CHECK. WDYT? I think some of the tests may be relying

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

* Eric Blake wrote on Mon, Aug 23, 2010 at 04:35:18PM CEST: > On 08/20/2010 10: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)? > >

[PATCH 2/2] doc: index entries for non-environment, non-output variables.

e and testsuite scripts. Fix entry for `tmp'. Signed-off-by: Ralf Wildenhues --- ChangeLog |8 doc/autoconf.texi | 18 -- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index a7ff0a5..e36b261 100644 --- a/ChangeLog +++ b

[PATCH 1/2] doc: minor indexing update.

: Ralf Wildenhues --- ChangeLog | 10 ++ doc/autoconf.texi | 39 +-- 2 files changed, 31 insertions(+), 18 deletions(-) diff --git a/ChangeLog b/ChangeLog index 0c3e5d4..a7ff0a5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,13 @@ +2010-09-05

two small doc patches for doc index

I've been looking a bit into the texinfo indexing stuff, see for an interesting thread that also highlights some problems with autoconf's massive use of indices. Anyway, let's start off with two small patches that fix a few very minor glit

Re: plans?

* Paolo Bonzini wrote on Tue, Aug 31, 2010 at 12:22:17PM CEST: > We _really_, _really_ need a stable branch of Autoconf where every > regression is treated the same way as security problems and released > in a matter of days. And where only regressions are fixed using the > _least invasive_ approa

  1   2   3   4   5   6   7   8   9   10   >